How does the skill detect if I'm in the wrong repository?

It scans your directory structure (e.g., specs/ vs src/), file patterns, and active plugin configurations to identify mismatches between your repo type and current task keywords.

What is a 'Brain' repository?

A Brain repository is a specialized space for strategy, specifications, roadmaps, and architectural decision records (ADRs) rather than production source code.

Can I use this with any Claude Code project?

Yes, it is compatible with Claude Code and works best when integrated with the Violet AI plugin ecosystem to manage complex agent workflows.

What happens if I trigger a High severity warning?

The skill will provide a strong warning and recommend switching to the appropriate repository type to ensure that planning or implementation is documented in the correct location.

Does this support custom naming conventions?

Yes, while it looks for common patterns like '-brain' or 'Service', it primarily uses a combination of file markers and plugin logic to determine the context.

Repository Context Checker

Name: Repository Context Checker
Author: violetio

byvioletio

•

Productivity & Workflow

Ensures developers are working in the appropriate repository type by detecting planning versus implementation context mismatches.

About

The Repository Context Checker is a specialized workflow skill for Claude Code designed to prevent architectural drift and planning sprawl within production codebases. By analyzing directory structures, plugin configurations, and conversation keywords, it identifies whether a user is working in a 'Brain' repository (focused on strategy, specifications, and ADRs) or a 'Code' repository (focused on implementation and deployment). This skill provides real-time guidance and tiered warnings when high-level planning is attempted in a production environment or vice versa, ensuring that strategic documentation remains centralized while code repositories stay focused on execution.

Key Features

Keyword-based task detection for planning and implementation phases
Real-time analysis of plugin configurations and agent roles
Guided workflow recommendations for transitioning between strategy and code
Multi-level severity warnings (High, Medium, Low) for context mismatches
1 GitHub stars
Automatic repository type detection (Brain vs. Code)

Use Cases

Preventing architectural 'should we' discussions from cluttering service-level repositories
Ensuring developers reference an approved specification before starting implementation
Standardizing the separation of concerns between product strategy and technical execution

About

Key Features

Keyword-based task detection for planning and implementation phases
Real-time analysis of plugin configurations and agent roles
Guided workflow recommendations for transitioning between strategy and code
Multi-level severity warnings (High, Medium, Low) for context mismatches
1 GitHub stars
Automatic repository type detection (Brain vs. Code)

Use Cases

Preventing architectural 'should we' discussions from cluttering service-level repositories
Ensuring developers reference an approved specification before starting implementation
Standardizing the separation of concerns between product strategy and technical execution