qa-orchestrator
Installation
SKILL.md
QA Orchestrator
When to Use
- Complex tasks that require multiple evidence-backed steps and human approval between stages.
Workflow
- Locate:
source-search/code-navigation - Understand:
file-reader/explain-code - Simulate:
safe-edit-simulator(dry-run + risk checklist) - Implement:
patch-applier+code-formatter(after approval) - Verify:
test-runner,linter-runner,static-analysis
Rules
- Keep each step small and reviewable; require explicit user approval for destructive or high-risk changes.
- Provide
path:lineevidence for key claims.
Related skills
More from pilinux/gorest
file-reader
Precisely read source files or snippets and return concise, citation-backed facts needed for decisions or edits.
28code-navigation
Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.
7fix-suggester
Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
7build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
7logs-repro-harness
Reduce flaky or environment-dependent failures to a minimal, reproducible script and capture the exact logs and error lines.
7ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
6