What is the difference between a Brain repo and a Code repo?

A Brain repo is dedicated to planning, containing specifications, ADRs, and roadmaps. A Code repo is dedicated to implementation, containing source code, tests, and deployment configurations.

What triggers a High severity warning?

A High warning occurs when you attempt major planning or 'redesign' tasks in a code repository without referencing an existing specification or approved ADR.

How does the skill know if I am doing planning work?

It scans your prompts for keywords like 'should we', 'architecture', 'roadmap', or 'trade-off' which indicate high-level decision-making rather than direct code implementation.

Does this skill prevent me from writing code in a Brain repo?

It won't block you, but it will provide a 'Low' severity suggestion to move implementation-focused work to the corresponding Code repo to maintain repository integrity.

Repository Context Checker

Name: Repository Context Checker
Author: violetio

byvioletio

Productivity & Workflow

Ensures developers work in the correct environment by distinguishing between planning-heavy brain repositories and implementation-focused code repositories.

About

The Repository Context Checker is an intelligent workflow guardrail for Claude Code that prevents the common anti-pattern of performing architectural planning within implementation-focused codebases. By analyzing directory structures, plugin configurations, and developer intent through natural language keyword detection, it identifies whether a workspace is a strategic 'brain' repository (containing specs, ADRs, and roadmaps) or a tactical 'code' repository (containing source code and deployment configs). The skill provides real-time, severity-based feedback to ensure that high-level decisions are documented in the right place before implementation begins, maintaining a clean separation between architecture and execution.

Key Features

Automatic detection of Brain vs. Code repository types based on file structures
0 GitHub stars
Severity-based warning system for high-risk context mismatches
Workflow recommendations for moving between planning and coding phases
Integration with .claude/settings.json to monitor active AI agent roles
Real-time analysis of task intent using planning vs. implementation keywords

Use Cases

Ensuring implementation tasks are executed in environments with the correct tech-stack plugins
Preventing developers from starting complex architectural changes without an approved specification
Guiding the creation of ADRs and roadmap items in dedicated documentation repositories

About

Key Features

Automatic detection of Brain vs. Code repository types based on file structures
0 GitHub stars
Severity-based warning system for high-risk context mismatches
Workflow recommendations for moving between planning and coding phases
Integration with .claude/settings.json to monitor active AI agent roles
Real-time analysis of task intent using planning vs. implementation keywords

Use Cases

Ensuring implementation tasks are executed in environments with the correct tech-stack plugins
Preventing developers from starting complex architectural changes without an approved specification
Guiding the creation of ADRs and roadmap items in dedicated documentation repositories