engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
- Installs
- 98
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/gentleman-programming/engram --skill engram-testing-coverage- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads engram-testing-coverage automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
When to Use
Use this skill when:
- Adding new behavior
- Fixing a bug
- Refactoring logic with branch complexity
TDD Loop
- Write a failing test for the target behavior.
- Implement the smallest code to pass.
- Refactor while keeping tests green.
- Add edge/error-path tests before closing.
Coverage Rules
- Cover happy path + error paths + edge cases.
- Prefer deterministic tests over flaky integration paths.
- Add seams only when branches are impossible to trigger naturally.
- Keep runtime behavior unchanged when adding seams.
Verification Ownership
Verification is evidence about the candidate; CI is the automated execution venue, not a substitute for local focused evidence.
- For behavior changes, run a focused regression test and tests for the affected package(s) locally before proposing the change. Report the commands and outcomes.
- Use targeted coverage when useful to find missed behavior or branches. Do not require a numeric coverage target or total module coverage for every PR.
- After the candidate is pushed to a PR, GitHub CI owns the full unit suite (
go test ./...), E2E suite (go test -tags e2e ./internal/server/...), lint, and applicable platform checks. Do not report CI evidence until those checks actually run. - When there is no PR or the candidate is unpushed, or when risk justifies more verification, run the additional applicable checks locally. Report checks that could not run as missing evidence rather than claiming CI covered them. Avoid duplicating the broad suite locally by default when PR CI will run it.
FAQ
What does the engram-testing-coverage skill do?
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
How do I install engram-testing-coverage?
Run npx skills add https://github.com/gentleman-programming/engram --skill engram-testing-coverage in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/engram-testing-coverage/ (personal) or .claude/skills/engram-testing-coverage/ (project).
Which AI agents can use engram-testing-coverage?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is engram-testing-coverage safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains engram-testing-coverage?
It is published by gentleman-programming in gentleman-programming/engram. It has 98 recorded installs.
More from gentleman-programming/engram
engram-memory-protocol
gentleman-programming/engram
Persistent memory discipline for Engram contributors. Trigger: Decisions, bugfixes, discoveries, preferences, or session closure.
engram-memory
gentleman-programming/engram
Open the skill to read its SKILL.md instructions.
engram-branch-pr
gentleman-programming/engram
Open the skill to read its SKILL.md instructions.
engram-sdd-flow
gentleman-programming/engram
Open the skill to read its SKILL.md instructions.
engram-docs-alignment
gentleman-programming/engram
Documentation alignment rules for Engram. Trigger: Any code or workflow change that affects user or contributor behavior.
gentleman-bubbletea
gentleman-programming/engram
Open the skill to read its SKILL.md instructions.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work