engram-testing-coverage

SkillDev tools

Lets your agent follow TDD and coverage rules when changing code in the Engram project.

Then ask your AI: use the engram-testing-coverage skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

About this skill

TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.

What this skill tells your AI

The instructions your AI receives, as published by gentleman-programming/engram in skills/testing-coverage/SKILL.md and read by Ahel’s review.

Use this skill when:

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.

Advanced