bruhook
Context tracking and plan enforcement system. Use when working on long coding sessions with plans.
When & Why to Use This Skill
bruhook is a specialized Claude skill designed for context tracking and plan enforcement during extended coding sessions. It acts as a background monitor that reviews code changes against a predefined plan, logs architectural drift, and ensures all project requirements are met before completion. By automatically restoring context and session-to-plan mappings, it prevents the AI from losing focus during long-running tasks or context window compactions, significantly improving the reliability of agentic software engineering.
Use Cases
- Maintaining continuity in multi-step software development tasks by automatically restoring plan context and review logs upon session resumption.
- Enforcing architectural integrity by reviewing every file change against the project plan to detect and log unintended implementation drift in real-time.
- Ensuring project completion through automated verification of git diffs against the original plan, preventing premature session termination when steps are missing.
- Managing complex refactoring projects where background monitoring is required to track progress across multiple files and maintain a consistent state.
| name | bruhook |
|---|---|
| description | Context tracking and plan enforcement system. Use when working on long coding sessions with plans. |
bruhook - Context Tracking System
bruhook is a buddy system that runs in the background during your coding sessions. It helps maintain context, track progress, and prevent incomplete work.
What bruhook does
When BRUHOOK_ENABLED=true:
Code review - Every file change is reviewed against the plan by a background Claude session. Drift (justified or not) gets logged.
Plan tracking - Session-to-plan mappings are stored in
.bruhook/session-plans.jsonin the project directory.Context restoration - On session resume or compaction, the plan and review log are automatically injected back into context.
Completion checking - When you try to stop, bruhook verifies the plan is actually complete. If steps are missing, it blocks the stop and tells you what's left.
Where to find things
- Plan file: Usually in
~/.claude/plans/*.md- the current session's plan - Review log:
.bruhook/reviews/{plan-name}.login the project directory - Session mapping:
.bruhook/session-plans.jsonin the project directory
How to check status
Use /bruhook:status to see:
- Current plan file for this session
- Whether bruhook is enabled
- Path to the review log
Use /bruhook:log to read the review log for the current session.
Important behaviors
- The plan tracker ALWAYS runs (even without
BRUHOOK_ENABLED) to maintain session-plan mappings - Review logs use numbered entries
[N]that build incrementally - The completion checker examines
git diffto verify actual implementation matches claims - Any drift from the plan is logged, whether justified or not