bp-context

Detect project stacks and generate or audit CLAUDE.md files across repositories.

4|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skaisser/blueprint --skill bp-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bp-context
Source: https://github.com/skaisser/blueprint/tree/main/skills/bp-context
Command: npx skills add https://github.com/skaisser/blueprint --skill bp-context

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Scan projects and automatically generate and audit CLAUDE.md files with stack auto-detection and Context7 docs.

Core Features & Use Cases

  • Auto-detects technology stack across directories and produces lean CLAUDE.md trees.
  • Audits existing CLAUDE.md files for staleness and suggests targeted updates.
  • Runs parallel workers per directory cluster to speed up documentation.
  • Reads blueprint/.config.yml to align language and stack, and integrates Context7 docs when available.

Quick Start

Run the bp-context skill on a repository to generate and audit CLAUDE.md docs across the project.

Frequently Asked Questions about bp-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate CLAUDE.md files for an existing project?

To auto-generate CLAUDE.md files, the skill scans your repository to detect the current technology stack and produces lean documentation trees across directories using parallel workers. It applies stack detection to populate each file with relevant context.

What is the best way to audit CLAUDE.md documentation for staleness?

Auditing CLAUDE.md files for staleness involves scanning existing documentation against the current project stack and README.md to identify outdated context. The skill then suggests targeted updates to align your documentation with the actual codebase.

Does generating CLAUDE.md require a specific configuration format?

Generating CLAUDE.md relies on reading the blueprint/.config.yml file to align language and stack settings. It also requires Context7 integration to pull accurate framework documentation during the project scan.

Can I detect and document multiple technology stacks across different directories?

Yes, you can document multiple stacks across directories because the skill runs parallel workers per directory cluster. This approach speeds up documentation generation and ensures each CLAUDE.md reflects its specific local context.

Why does my CLAUDE.md file not reflect my current tech stack?

Your CLAUDE.md may not reflect your current tech stack if it was created manually or lacks recent updates. The skill resolves this by scanning the project stack and auditing existing files to suggest targeted updates.