Menú
Wrapper skill that invokes the superharness qa CLI command from within the AI tool session.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Session start guide: explains how to use superharness skills and conventions. Injected by SessionStart hook.
Superharness brainstorming skill. You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Main entry point: end-to-end workflow for building features. Use /superharness:go 'requirement' to start. Orchestrates brainstorm → plan → TDD implementation → review → QA.
Infrastructure skill: start a local visualization server that renders Mermaid diagrams in the browser. Write .mmd files with pure Mermaid code, the browser updates in real-time via WebSocket (no page reload). Used by brainstorm, writing-plans, and other skills.
Surface unresolved decisions in a development request and ask the user before implementing. Use when starting a non-trivial dev task whose requirements leave open questions that would change the implementation (scope, data shape, UX behavior, compatibility), or when the user asks to confirm first ("先确认一下", "有不清楚的先问").
| name | sh-qa |
| description | Wrapper skill that invokes the superharness qa CLI command from within the AI tool session. |
Trigger external QA evaluation by calling the superharness qa CLI command.
This skill is a thin wrapper — it runs the CLI and reports results. The actual QA logic lives in the CLI.
superharness qa --task .superharness/tasks/{task}
This will:
qa-report.md (human-readable) to the task directoryqa-issues.json (machine-readable) to the task directoryRead and summarize qa-report.md for the user:
If issues were found:
"QA found {N} issues ({critical} critical, {major} major). Run
/superharness:sh-fixto address them."
If all passed:
"QA passed. Ready to finalize with
superharness:finishing-a-development-branch."
If no external QA services configured:
"No external QA services configured. Feedback layer checks (test/lint/typecheck) already ran during implementation. To add QA services, configure them in
.superharness/config.yamlunderqa.services."