harness

Plugin harness from marketplace main in vertexcover-io/harness-engineering. Commands read from the repo's manifest — 1 month ago.

Skills (30)

• adr

  Record an architecture decision as a permanent ADR in docs/adr/ that binds future code changes. The skill applies its own gates and drops what does not qualify, so send any candidate. Planning calls it for the task and every approved decision; also use it directly ("write an ADR", "record this decis

• code-quality

  High-quality code patterns with strict types, functional programming, and immutability. Use when writing ANY code in any language. Trigger whenever the user writes, reviews, or refactors code — even if they don't explicitly ask for "quality" or "strict" patterns. This skill applies to TypeScript, Py

• code-review

  Deep code review that hunts for subtle bugs and for code that works but should have been written differently. Runs eight reviewer personas in parallel, plus a Design persona when design/spec.md exists, aggregates their findings into a report, then applies the fixes and records them in it. Use when t

• coverage-guard

  Coverage diagnostic for a package. Use this skill after writing or modifying code to see which code is uncovered and which spec behaviors that maps to. Diagnostic only — reports and asks the user; never generates specs, never invokes orchestrate, never fails a build.

• doc-quality-guard

  Use when the user says "check docs", "audit docs", "doc quality", "doc slop", "stale docs", or wants to verify documentation accuracy and tone against the actual codebase.

• find-factors

  Identify the factors that change an existing product flow's behavior or outcome. Use when a user wants to understand what influences a flow; inspect the implementation and present the full factor list within the agreed scope.

• functional-verify

  Verify a feature actually works by driving it — the gate between "tests are green" and "feature is done" — MUST run before claiming a feature complete, opening a PR, or committing, and whenever orchestrate enters its verify stage. Passing unit and e2e tests are not verification. Trigger on "tests pa

• git-commit

  Analyzes dirty working trees, groups related changes into logical commits using hunk-level staging, and writes conventional commit messages. Use when the user asks to commit their changes or split them into separate commits, including \"save my work to git\" or \"organize my git changes\". Does not

• git-pr

  Create or update a pull request with a clear title, visual change outline, and validation evidence. Use when asked to raise a PR, improve a PR description, or from the orchestrate Commit & PR stage after pushing.

• harness-retro

  Audit a finished harness pipeline run and report the harness defects it exposed. Reads the run's session transcripts, finds what broke, and writes one ranked report for the people who build the harness. Use this skill whenever a pipeline run ends or aborts, and whenever the user says "retro", "retro

• implement

  Implement a requested change, plan, phase, or review feedback using test-first development. Runs directly in the current conversation or inside an orchestrate worker.

• learn

  Capture learnings as clean, human-readable lesson docs in .harness/knowledge/lessons/. Use after solving a non-trivial problem, discovering a design pattern, hitting a gotcha, or making an architectural decision worth remembering. Triggers on: 'document this', 'capture this learning', 'that was tric

• library-probe

  Trust gate that validates every external library/API named in design.md *before* the plan is built. Runs cheap health heuristics, then a use-case smoke test against the live service using credentials from project-root `.env.harness` (gitignored). Produces `.harness/<name>/library-probe.md` with a pe

• orchestrate

  Orchestrate end-to-end development from a task to an open PR through a multi-agent pipeline. Use when the user says orchestrate, run the pipeline, or full workflow; supplies a prompt, ticket, PRD, or design document to take to a PR; or passes --auto for an unattended CI run.

• planning

  Grill the open forks, checkpoint the solution inline, then build plan.html for review — one stage from idea to approved plan. Use for code work that needs thought before code ("plan this", "how should we implement"), and to interrogate an existing design or PRD ("grill this idea"). Runs as orchestra

• project-scaffold

  Scaffold a full TypeScript project from a tech stack spec document. Creates Turborepo workspace, all packages with starter code, Podman Compose for local infra (PostgreSQL, Redis, etc.), and verifies the setup builds and runs. Use this skill whenever the user wants to set up a new TypeScript project

• quality-gate

  Post-stage verification with hard pass/fail thresholds. Every claim backed by verbatim command output — no check may be silently absent, skipped, or weakened. Runs after TDD, refactor, and before PR. Reads each package's commands from orchestrate.config.json and its baseline metrics from .harness/<S

• refactor

  Refactoring assessment and patterns. Use after tests pass (GREEN phase) to assess improvement opportunities, or when the user explicitly asks to refactor code. Guides what to look for, how to prioritize, and which techniques to apply. Trigger this skill whenever refactoring is mentioned, when assess

• regression-tests

  Discover regression scenarios for an existing user flow, obtain plan approval through Plannotator, delegate test implementation, require test review, then commit and open a PR. Use when a user wants regression tests for a product flow taken through reviewed delivery.

• resolve-merge-conflict

  Resolves git merge and rebase conflicts, stopped locally or reported on an open pull request, by recovering the intent behind each conflicting change, then finishing the merge. Use when a merge, rebase, cherry-pick or stash pop has stopped with conflicts, when git reports 'CONFLICT', 'Unmerged paths

• review-fixer

  Automated PR review fixer. Reads human code review comments, classifies each as a direct fix or orchestration task, applies fixes, runs quality gate, commits, pushes, and comments back on the PR. Designed to run in GitHub Actions via claude-code-action. Trigger when the prompt contains review commen

• rework

  Apply QA or PR-review feedback to a ticket, across every PR it carries.

• setup-harness

  Set up the harness in a repo. Runs the doctor, fixes what can be fixed here, resolves any standing instruction that would pause an unattended run, hands the user what only they can do, and writes the project's `orchestrate.config.json`. Use when the user says 'set up the harness', is running a harne

• skill-eval-generator

  Generates eval test suites (evals.json + fixture files) for any skill by analyzing its SKILL.md. Use when the user says "generate evals for X", "create tests for X skill", "write evals", "eval suite for X", or wants to create test coverage for a skill before running skill-creator eval. Also trigger

• skill-review

  Reviews an agent skill against a rubric covering description quality, invocation, structure, integrity, coherence, test coverage, security, content, convention and cost, then writes a report plus machine-readable findings. Use whenever the user asks to review, audit, critique, grade, score or sanity

• sync-docs

  Synchronizes documentation with code changes. Scans for stale, missing, or contradictory docs, then updates them to reflect the actual implementation. Structures docs for both human readability and AI consumption. Use after code changes are complete and quality gate has passed — before committing.

• tdd

  Test-Driven Development. Use for any implementation task — features, bug fixes, refactoring — whenever the project's CLAUDE.md signals TDD (mentions of TDD, test-driven, RED-GREEN-REFACTOR, "tests first"), or when the user asks for test-first work. Load before writing any production code. Its refere

• tech-debt-finder

  Use when the user says "find tech debt", "audit code quality", "what needs cleanup", "show me debt", "code health check", "scan for smells", or wants a comprehensive quality assessment before planning a refactor or sprint.

• using-git-worktrees

  Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

• writing-style

  How to write any document a person will read — reports, plans, PR and issue bodies, READMEs, release notes, summaries. Use whenever you write or edit prose for a human reader. Trigger before writing a report, a plan, a summary, a commit or PR description, or documentation — even when the user never

Hooks (7)

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/dashboard/ask-user-hook.mjs" pre 2>/dev/null || true

• PreToolUse

  node "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-history.mjs" 2>/dev/null || true

• PostToolUse

  node "${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/dashboard/ask-user-hook.mjs" post 2>/dev/null || true

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/dashboard/dag-update.mjs" finalize interrupted 2>/dev/null || true

• Stop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-history.mjs" 2>/dev/null || true

• SubagentStop

  node "${CLAUDE_PLUGIN_ROOT}/hooks/artifact-history.mjs" 2>/dev/null || true

• SessionEnd

  node "${CLAUDE_PLUGIN_ROOT}/skills/orchestrate/dashboard/dag-update.mjs" finalize interrupted 2>/dev/null || true

Similar plugins