ctx

Record a coding convention. Use when a repeated pattern should be codified so all sessions follow it consistently.

Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.

Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.

Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.

Load full context packet. Use at session start or when context seems stale or incomplete.

Enrich architecture artifacts with code intelligence data. Takes existing /ctx-architecture output as baseline, verifies and quantifies with GitNexus MCP (blast radius, execution flows, domain clustering, registration sites). Run after /ctx-architecture, not instead of it.

Build and maintain architecture maps. Use to create or refresh ARCHITECTURE.md and DETAILED_DESIGN.md. Supports principal mode for deeper analysis: vision, future direction, bottlenecks, implementation alternatives, gaps, upstream proposals, and intervention points.

Archive completed tasks. Use when TASKS.md has many completed items cluttering the view.

Generate themed blog post from commits. Use when writing about changes between releases or documenting a development arc.

Generate blog post draft. Use when documenting project progress, sharing learnings, or writing about development experience.

Design before implementation. Use before any creative or constructive work (features, architecture, behavior changes) to transform vague ideas into validated designs.

Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.

Review code changes for correctness, edge cases, and convention adherence. Use when the user asks to review code, a diff, a PR, or says 'review this'.

Commit with context persistence. Use instead of raw git commit to capture decisions and learnings alongside code changes.

Consolidate redundant entries in LEARNINGS.md or DECISIONS.md. Use when ctx drift reports high entry counts or entries overlap.

Troubleshoot ctx behavior. Runs structural health checks, analyzes event log patterns, and presents findings with suggested actions.

Detect and fix context drift. Use to find stale paths, broken references, and constitution violations in context files.

Explain code for someone new to the project. Use when the user asks 'what does this do', 'explain this', or wants to understand unfamiliar code.

Browse session history. Use when referencing past discussions or finding context from previous work.

Execute a plan step-by-step with verification. Use when you have a plan document and need disciplined, checkpointed implementation.

Import Claude Code plan files into project specs. Use when plan files in ~/.claude/plans/ should become permanent project specs.

Full journal pipeline: import unimported sessions, then batch-enrich all unenriched entries. Use when the user says 'process the journal' or to catch up on the backlog.

Enrich journal entry with metadata. Use when journal entries lack frontmatter, tags, or summary for future reference.

Generate a shell script for running AI tools in autonomous iteration loops. Use when setting up unattended iteration, headless agent runs, or CI-driven AI workflows.

Suggest what to work on next. Use when starting a session, finishing a task, or when unsure what to prioritize.

Manage encrypted scratchpad. Use for short, sensitive one-liners that travel with the project.

Pause context hooks for this session. Use when context nudges aren't needed for the current task.

Audit prompting patterns. Use periodically to help users improve prompt quality and reduce clarification cycles.

Refactor code safely: test-first, one change at a time, preserve behavior. Use when the user says 'refactor this', 'clean this up', or wants structural improvement.

Reflect on session progress. Use at natural breakpoints, after unexpected behavior, or when shifting to a different task.

Recall project context and present structured readback. Use when the user asks 'do you remember?', at session start, or when context seems lost.

Manage session reminders. Use when the user says 'remind me to...' or asks about pending reminders.

Resume context hooks after a pause. Use when the user says 'resume ctx', 'unpause', 'turn nudges back on', or when transitioning from a quick task back to project work.

Audit settings.local.json for dangerous permissions. Use periodically, after granting permissions, or when security hygiene matters.

Audit skills against Anthropic prompting best practices. Use when reviewing skill quality, after creating or modifying a skill, before releasing skills, or when a skill produces inconsistent results. Also use when the user says 'audit this skill', 'check skill quality', 'review the skills', or 'are our skills any good?'

Create, improve, and test skills. Use when building a new skill, evaluating or fixing an existing one, turning a conversation workflow into a reusable skill, or when a skill is not triggering or producing poor results. Also use when the user says 'turn this into a skill', 'make a slash command for this', or 'this should be a skill'.

Scaffold a feature spec from the project template. Use when planning a new feature, writing a design document, or when a task references a missing spec.

Show context summary. Use at session start or when unclear about current project state.

Manage git worktrees for parallel agent development. Use when splitting work across independent task tracks.

End-of-session context persistence ceremony. Use when wrapping up a session to capture learnings, decisions, conventions, and tasks.

21 hooks across 3 events