// Activate when starting new work to check for established patterns. Activate when ensuring consistency with team standards or when promoting successful memory patterns. Searches and applies best practices before implementation.
Activate when user wants to save knowledge, search past decisions, or manage persistent memories. Handles architecture patterns, implementation logic, issues/fixes, and past implementations. Uses local SQLite + FTS5 + vector embeddings for fast hybrid search. Supports write, search, update, archive, and list operations.
Activate when user explicitly requests the development workflow process, asks about workflow phases, or says "start work", "begin development", "follow the process". Activate when creating PRs or deploying to production. NOT for simple questions or minor fixes. Executes AUTONOMOUSLY - only pauses when human decision is genuinely required.
Activate when reviewing code, before committing, after committing, or before merging a PR. Activate when user asks to review, audit, check for security issues, or find regressions. Analyzes code for logic errors, regressions, edge cases, security issues, and test gaps. Fixes findings AUTOMATICALLY. Required at process skill quality gates.
Activate when user asks to commit, push changes, create a PR, open a pull request, or submit changes for review. Activate when process skill reaches commit or PR phase. Provides commit message formatting and PR structure. PRs default to dev branch, not main. Works with git-privacy skill.
Activate when asked to auto-review and merge a PR. Runs a closed-loop workflow: subagent Stage 3 review -> fix findings -> re-review -> post ICC-REVIEW receipt -> merge (optional via workflow.auto_merge).
Activate when user asks to release, bump version, cut a release, merge to main, or tag a version. Handles version bumping (semver), CHANGELOG updates, PR merging, git tagging, and GitHub release creation.
| name | best-practices |
| description | Activate when starting new work to check for established patterns. Activate when ensuring consistency with team standards or when promoting successful memory patterns. Searches and applies best practices before implementation. |
Search and apply established best practices before implementation.
Best practices are stored in best-practices/<category>/:
best-practices/architecture/best-practices/development/best-practices/git/best-practices/operations/best-practices/quality/best-practices/security/best-practices/collaboration/MANDATORY: Check best-practices AND memory before starting work:
Identify the domain/category of work
Search best-practices directory:
find best-practices/<category>/ -name "*.md"
Search memory for related patterns:
memory search: "<relevant keywords>"
(CLI fallback: node ./.claude/skills/memory/cli.js search "<relevant keywords>" for project installs,
or node ~/.claude/skills/memory/cli.js search "<relevant keywords>" for user installs.)
Apply established patterns to implementation
Note deviations with justification
# [Practice Name]
## When to Use
[Situations where this practice applies]
## Pattern
[The recommended approach]
## Example
[Concrete implementation example]
## Rationale
[Why this approach is preferred]
## Anti-patterns
[What to avoid]
When a memory pattern proves successful:
When creating AgentTasks, reference applicable best practices:
context:
best_practices:
- category: security
practice: input-validation
- category: git
practice: commit-messages
| Category | Focus |
|---|---|
| architecture | System design patterns |
| collaboration | Team workflow patterns |
| development | Coding standards |
| git | Version control practices |
| operations | Deployment/monitoring |
| quality | Testing/review practices |
| security | Security patterns |