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.
Deep technical review protocol for Engram pull requests. Trigger: Reviewing any external or internal contribution before merge.
$ npx -y skills add Gentleman-Programming/engram --skill pr-review-deep --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/pr-review-deepContext preview
The summary Claude sees to decide when to auto-load this skill.
Deep technical review protocol for Engram pull requests. Trigger: Reviewing any external or internal contribution before merge.
name: engram-pr-review-deep description: > Deep technical review protocol for Engram pull requests. Trigger: Reviewing any external or internal contribution before merge. license: Apache-2.0 metadata: author: gentleman-programming version: "1.0"
Use this skill when:
---
1. Read full diff, not only summary. 2. Run relevant tests locally. 3. Validate API/contracts and migration safety. 4. Check docs against implementation. 5. Flag commit hygiene violations.
---
Merge only when:
Otherwise request changes with actionable items.
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.