memory
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
$ npx -y skills add Gentleman-Programming/engram --skill testing-coverage --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/testing-coverageContext preview
The summary Claude sees to decide when to auto-load this skill.
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
name: engram-testing-coverage description: > TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
Use this skill when:
---
1. Write a failing test for the target behavior. 2. Implement the smallest code to pass. 3. Refactor while keeping tests green. 4. Add edge/error-path tests before closing.
---
---
Run:
go test ./... go test -cover ./...
Report package coverage and total coverage in the PR.
Persistent memory system for AI coding agents. Agent-agnostic Go binary with SQLite + FTS5, MCP server, HTTP API, CLI, and TUI.
Repo: Gentleman-Programming/engram
ALWAYS ACTIVE — Persistent memory protocol. You MUST save decisions, conventions, bugs, and discoveries to engram proactively. Do NOT wait for the user to ask.
Architecture guardrails for Engram across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state…
Backlog triage protocol for Engram: audit open issues and PRs, classify each item, infer maintainer ideology from comments, and produce an actionable…
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for…
Product and business-rule guardrails for Engram. Trigger: Any change that affects sync behavior, project controls, permissions, or memory semantics.
Commit and branch naming standards for Engram contributors, enforced by GitHub rulesets. Trigger: Any commit creation, review, or branch cleanup.