skill-ao92265-claude-code-playbook-test-first · by Install
$ agentstack add skill-ao92265-claude-code-playbook-test-first ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ao92265-claude-code-playbook-test-first) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Test-First Development
Enforce the Red-Green-Refactor cycle. Tests define the contract before implementation begins.
Steps
- Understand the requirement:
- Clarify what the feature/fix should do
- Identify inputs, outputs, edge cases, and error conditions
- Ask clarifying questions if the spec is ambiguous
- Write failing tests (RED):
- Create test file(s) if they don't exist
- Write test cases that define expected behavior
- Include happy path, edge cases, and error cases
- Tests should be specific and descriptive — test names explain the contract
- Confirm tests fail for the right reason (NON-NEGOTIABLE):
- Run the test suite:
npm test,pytest,go test, etc. - Verify failures are "function not found" or "wrong return value" — not syntax errors
- If tests fail for the wrong reason, fix the test first
- Never skip this step. Tests that go green on first run are tautological or mocked the behavior under test. A test you never watched fail is theater, not verification.
- Implement minimum code to pass (GREEN):
- Write the simplest code that makes all tests pass
- Do not optimize or generalize yet
- Do not add code that isn't required by a test
- Confirm all tests pass:
- Run the full test suite
- All new tests must be green
- All existing tests must still pass (no regressions)
- Refactor (REFACTOR):
- Clean up implementation while keeping tests green
- Extract helpers, rename variables, simplify logic
- Run tests after each refactoring step
- Final verification:
- Run full test suite one last time
- Run type checker / linter if applicable
- Show the user the test results and implementation summary
Important
- Never skip the RED step. If you can't write a failing test first, you don't understand the requirement well enough.
- Never write implementation before tests exist. The test defines the contract.
- Keep tests fast. Prefer unit tests over integration tests where possible.
- One behavior per test. Each test should verify exactly one thing.
- Test names are documentation. Use descriptive names:
should_return_404_when_user_not_found.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ao92265
- Source: ao92265/claude-code-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.