Automates quality assurance for docket CLI by running functional tests and validating binary output.
Install
mkdir -p .claude/skills/qa-alt-f4-llc && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13189" && unzip -o skill.zip -d .claude/skills/qa-alt-f4-llc && rm skill.zipInstalls to .claude/skills/qa-alt-f4-llc
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Run quality assurance checks on the docket CLI binary. Use this skill when the user asks to "run QA", "test the build", "verify the binary", "smoke test", "run quality assurance", "check the CLI", or wants to validate that docket is working correctly after a build.Key capabilities
- →Build the docket CLI binary
- →Run functional checks across all commands and flags
- →Validate output, exit codes, and error handling
- →Verify JSON contracts
- →Generate a structured pass/fail report
- →Clean up temporary directories after tests
How it works
The skill executes a `qa.sh` script that builds the docket binary if not provided, runs functional checks across all commands, validates outputs and contracts, and then prints a pass/fail report.
Inputs & outputs
When to use qa
- →Verify CLI build
- →QA test docket
- →Smoke test binary
About this skill
Docket QA Skill
Run the docket QA test suite by executing the reusable scripts/qa.sh script.
This script builds docket, runs all functional checks across every command and
flag, validates output, exit codes, error handling, and JSON contracts, then
prints a structured pass/fail report.
ARGUMENTS: optional path to the docket binary. If not provided, the script builds from source automatically.
Workflow
1. Run the QA script
./scripts/qa.sh [optional-binary-path]
The script handles everything:
- Builds docket (if no binary path given)
- Creates isolated temp directories so tests don't affect user state
- Runs all test sections in order (A through S)
- Cleans up temp directories on exit
- Prints a full pass/fail report with details on failures
- Exits 0 if all checks pass, 1 if any fail
2. Review the output
The script prints a summary table and final result line:
QA Result: X/Y checks passed
If any checks failed, they are listed at the bottom for visibility.
3. Report results to the user
Summarize the QA results. If there are failures, investigate and fix them.
Test Coverage
The script covers these sections (see scripts/qa.sh for full details):
| Section | Description | Checks |
|---|---|---|
| A | No-DB commands (version, help, config) | 5 |
| B | Init lifecycle | 4 |
| C | Config after init | 2 |
| D | DOCKET_PATH override | 3 |
| E | Quiet mode | 2 |
| F | Create command | 11 |
| G | List command (filters, sorting, tree) | 12 |
| H | Show command | 6 |
| I | Move command (status transitions) | 11 |
| J | Close command | 6 |
| K | Reopen command | 6 |
| L | Edit command (all flags) | 15 |
| M | Edit reparenting (cycles, self-ref) | 11 |
| N | Delete — simple | 5 |
| O | Delete — cascade and orphan | 16 |
| P | Activity log verification | 6 |
| Q | JSON contract validation | 11 |
| R | Exit codes (all commands) | 23 |
| S | Error paths (no DB) | 10 |
Developer Usage
Developers can run the script directly without Claude:
# Build and test
./scripts/qa.sh
# Test a specific binary
./scripts/qa.sh /path/to/docket
# After a vorpal build
vorpal build docket --export
./scripts/qa.sh ./result/bin/docket
Requires jq to be installed for JSON validation.
When not to use it
- →When the user wants to fix issues
- →When the user wants to develop new features
- →When the user wants to deploy the binary
Prerequisites
Limitations
- →Requires `jq` for JSON validation
- →Only tests the docket CLI binary
How it compares
This skill automates a complete suite of QA tests for the docket CLI, providing a structured report that would otherwise require manual execution and verification of many individual checks.
Compared to similar skills
qa side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| qa (this skill) | 0 | 5mo | Review | Beginner |
| e2e-testing-patterns | 8 | 2mo | No flags | Intermediate |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| perf-lighthouse | 13 | 5mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
e2e-testing-patterns
wshobson
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
xcodebuildmcp
cameroncooke
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
verify
Use when you want to validate changes before committing, or when you need to check all React contribution requirements.
playwright-pro
alirezarezvani
Production-grade Playwright testing toolkit. Use when the user mentions Playwright tests, end-to-end testing, browser automation, fixing flaky tests, test migration, CI/CD testing, or test suites. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting.