harness

Plugin harness from marketplace waqas-harness in waqas1412/claude-harness. Commands read from the repo's manifest — 17 days ago.

Skills (9)

• harness-distill

  Distill durable learnings from recent sessions into proposed memory facts, CLAUDE.md lines or skill gotchas, verified and deduped. Proposes only. Use after a run that surfaced recurring friction.

• harness-init

  Generate a repo's CLAUDE.md index and .claude/repo-index deep indexes. Use once per repo that has none.

• orchestrate

  Run the review lenses over a change: pick the ones the change touches, read or dispatch each, gate go/no-go on cited evidence. Use when asked for our lenses, or to plan or verify a non-trivial change.

• pr-comments

  Triage unresolved review threads on an open PR: per thread either agree (fix, verify, push, reply, resolve) or disagree (justify with a version-matched citation). Use when asked about PR comments or told to reply and resolve.

• pr

  Write or draft a minimal GitHub PR title and body: a linked tracker close line, a short what-changed list, and how-to-test steps only when the reviewer has something to run, sized to the PR, in plain words. Use when running gh pr create / gh pr edit or when asked for a PR description.

• refresh-seams

  Refresh the cross-repo seam graph and the per-repo Cross-repo seams sections between their markers.

• sync-prs

  Sync open PRs with their real bases from gh, rebase in stack order, push --force-with-lease, report per-PR state. Hands conflicts back unresolved. Use for syncing a branch or PR with its base.

• ticket

  Write or draft a tracker ticket in product language: the core issue in two lines, a numbered middle, then a pair of results. Use when drafting any ticket or backlog item.

• workspace-init

  Scan every repo in the workspace and generate the global multi-repo index plus each repo's deep index.

Subagents (17)

• accessibility-auditor

  Accessibility of a BUILT UI: keyboard-only path, focus management and visibility, accessible names, semantics and roles, dialog/overlay behaviour, live-region announcement, reflow and target size.

• compatibility-auditor

  Whether a change breaks an existing consumer: API and status contracts, published schemas, migration reversibility, shared props and exported signatures, persisted state, event names, config, deploy ordering.

• data-flow-timing-auditor

  Cross-file data-flow timing and staleness: signals read before they settle, proxy gates, one-shot consumers snapshotting eventually-consistent state, init/hydration order, missed-event races.

• design-parity-auditor

  Implemented UI vs its pinned design source: token identity, auto-layout semantics, the state matrix, breakpoint fidelity, and the WCAG floors a DESIGN must not lose.

• design-principles-advisor

  Structural design principles: SOLID, GRASP, CUPID, coupling and cohesion, SoC, LoD, CQS, POLA.

• developer-reviewer

  Correctness and test review of a diff: logic bugs, nil/empty/ordering/boundary/timezone, invariants and contracts, test coverage, AGENTS.md and CLAUDE.md compliance.

• docs-researcher

  External knowledge from official primary sources: version-correct API usage, idioms, breaking changes and deprecations for this repo's actual dependencies.

• implementer

  Writes code to a brief already decided: applies the edits, runs the repo's lint, build and change-related tests, reports what changed with real command output. Carries no authority and never touches git state.

• jira-ticket-author

  Drafts a tracker ticket by following the /ticket skill template and the repo profile.

• performance-optimizer

  Performance and complexity: time/space Big-O, allocations, DB N+1 and indexes, concurrency, frontend render and bundle cost.

• pr-author

  Drafts a PR title and body by following the /pr skill template and the repo profile.

• principles-engineer

  Reuse, duplication and abstraction right-sizing: DRY, WET, AHA, KISS, YAGNI, and guarding against premature abstraction.

• security-auditor

  Authorization and tenant scoping, authentication and token handling, secret and sensitive-data exposure, injection and deserialization at real trust boundaries, unsafe defaults.

• senior-software-engineer

  Implementation craft: idiomatic code in the repo's primary languages and its conventions for error handling, data access and framework wiring. Advisory; the main loop owns edits.

• spec-fidelity-auditor

  Conformance of a change to its own spec: a bidirectional requirements trace, every criterion delivered with evidence, every diff hunk traced to a clause or dispositioned.

• system-architect

  Macro structure: where code should live, module boundaries, blast radius, structural cross-component contracts (shape, not timing), fit to repo patterns.

• system-designer

  Micro component spec once placement is decided: exact signatures, request and response shapes, algorithm steps, exhaustive edge-case matrix.

Hooks (10)

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-coauthor.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-pr-reviewer.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-force-push.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-md-emdash.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-workflow-rules.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-local-only-refs.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-external-query-leaks.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-external-query-leaks.sh"

• PreToolUse

  sh "${CLAUDE_PLUGIN_ROOT}/hooks/block-md-emdash.sh"

• PostToolUse

  python3 "${CLAUDE_PLUGIN_ROOT}/hooks/filter-verbose-output.py"

Similar plugins