By anicol
QA agents for Claude Code. Smart test runner, coverage analysis, test generation, and pre-push quality gates. Works with any language and test framework.
Run tests with coverage and report which changed lines are uncovered
Check QA readiness — framework detection, context files, tools, agent health, and feedback trends
Full QA pipeline — risk analysis, test, coverage, write tests for gaps, pre-push gate
Scaffold QA context files in your project
Install git hooks and Claude Code hooks for automatic QA on commit and push
Runs tests with coverage enabled, parses the coverage report, and reports which lines in your changed files are uncovered. Only shows coverage that matters — your diff, not the whole project.
One-stop quality gate before pushing. Runs lint, type checking, and affected tests. Reports pass/fail for each step with clear fix instructions.
Scores the risk of current changes (1-10) using a structured algorithm. Categorizes files, detects security/payment code, matches critical paths, and factors in change size.
Smart test runner that auto-detects frameworks, runs tests (all or affected), and returns structured results with pass/fail per test, timing, and actionable error details.
Finds code without test coverage and writes real, working tests. Reads the source code, understands the behavior, writes tests, runs them, and iterates until they pass.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Agentic QA pipeline for Claude Code. Risk-scores your changes, runs the right tests, finds coverage gaps, writes missing tests, and gates your push — all automatically.
Scout QA is a Claude Code plugin with 5 agents that form an adaptive QA pipeline:
real_bug / test_bug / flakyThe pipeline adapts to risk: a 2/10 docs change gets a quick test run. A 9/10 auth+payments change gets the full treatment.
# Add the marketplace
claude plugin marketplace add anicol/scout-qa
# Install the plugin
claude plugin install scout-qa
# Initialize context files in your project (inside Claude Code)
/scout:init
# Wire into your git pipeline
/scout:install-hooks
# Push with confidence
git push origin feature/your-branch
| Command | What It Does |
|---|---|
/scout:init | Scaffold context/qa/ files, auto-detect framework |
/scout:risk | Score risk of current changes (1-10) |
/scout:test [all|file] | Run tests (affected by default) |
/scout:coverage [all] | Coverage report on changed lines |
/scout:write-tests [file|--critical] | Generate tests for uncovered code |
/scout:pre-push | Quality gate (lint + types + tests) |
/scout:full-check | Risk-adaptive full pipeline |
/scout:install-hooks | Install git hooks + Claude Code hooks |
/scout:doctor | Health check — framework, tools, context files |
/scout:status | QA dashboard from agent state |
Three layers of automation, installed with /scout:install-hooks:
Layer 1 — Claude Code Hooks (during coding)
After Claude edits a source file, auto-runs the corresponding test. After git commit, suggests running tests.
Layer 2 — Git Pre-Commit (every commit) Lints staged files only. Fast, no AI, sub-second.
Layer 3 — Git Pre-Push (every push)
export SCOUT_MODE=smart): full Claude Code pipeline via claude -p "/scout:full-check"git push --no-verifyScout QA uses project-specific context files to make agents smarter over time. Run /scout:init to scaffold them.
context/qa/
├── test-strategy.md # Testing philosophy
├── conventions.md # Naming, assertions, mocking, quality bar
├── critical-paths.md # Business-critical code paths
├── coverage-policy.md # Coverage thresholds by tier
├── ownership.md # Who owns test coverage where
├── frameworks.md # Framework config (auto-populated)
├── risk-config.yaml # Risk weights and thresholds
├── autonomy.yaml # Agent permission config
└── learnings/
├── what-works.md # QA patterns proven effective
└── what-doesnt.md # QA anti-patterns to avoid
/scout:full-check adapts depth based on risk score:
| Risk Score | Pipeline Depth |
|---|---|
| 1-3 (Low) | Affected tests only |
| 4-6 (Medium) | Tests + changed-line coverage |
| 7-10 (High/Critical) | Tests + coverage + write tests for gaps + pre-push gate |
Auto-detected from your project files:
| Category | Supported |
|---|---|
| Test | Jest, Vitest, Pytest, Go test, RSpec, Cargo test, Mocha, Minitest |
| Lint | ESLint, Ruff, golangci-lint, RuboCop |
| Types | TypeScript, MyPy, Pyright |
| Capability | Vanilla Claude Code | With Scout QA |
|---|---|---|
| Risk scoring | Ad-hoc opinion | Deterministic 1-10 with weighted factors |
| Failure analysis | Describes the error | Classifies real_bug / test_bug / flaky |
| QA depth | Same effort always | Adapts to risk score |
| Coverage | Whole-project dump | Changed lines only |
| Test conventions | Re-learns each session | Persisted in context files |
| Flaky tests | Forgotten | Tracked across sessions |
| Quality gate | Manual | Structured PASS/FAIL on push |
| Git integration | None | Pre-commit + pre-push hooks |
npx claudepluginhub anicol/scout-qa --plugin scout-qa6 engineering management agents for Claude Code. Spec generation, ticket decomposition, risk detection, review orchestration, release management, and sprint retrospectives.
Test framework detection, convention-aware test generation, and changed-file test execution.
Agentic Quality Engineering — AI-powered QE platform with 60 specialized agents, 75+ skills, sublinear coverage analysis, ReasoningBank pattern learning, and deep MCP integration for Claude Code and 11 coding agent platforms
Agents specialized in quality assurance, testing strategies, and test architecture. Focuses on ensuring code quality and reliability.
Generate comprehensive tests for a specific file
Analyze code coverage metrics, identify untested code, and generate comprehensive coverage reports
Write comprehensive tests covering happy/edge/error/concurrency paths. Verifies tests actually catch bugs.