repairing-project-setup

Audits and repairs broken CLAUDE.md and AGENTS.md agent configuration files against a canonical specification.

5|Updated Nov 9, 2025
One-click install
npx skills add https://github.com/britt/agent-skills --skill repairing-project-setup-britt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repairing-project-setup
Source: https://github.com/britt/agent-skills/tree/main/skills/repairing-project-setup
Command: npx skills add https://github.com/britt/agent-skills --skill repairing-project-setup-britt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent instruction files in a repository often end up broken, half-finished, or drifted: a setup run failed partway, CLAUDE.md or AGENTS.md is thin or missing sections, unfilled {{PLACEHOLDER}} text remains, AGENTS.md is a symlink, or the two files disagree. This Skill audits the repo against the target state defined by the setting-up-a-project skill and repairs only the gaps, preserving decisions already recorded. ## Core Features & Use Cases - 15-Point Audit Table: Runs checks covering file existence, symlink defects, placeholder text, verbatim rule-file diffs, cross-file agreement, and whether documented commands actually run, recording PASS / FAIL / N-A before touching anything. - Delta-Only Repair: Merges missing sections into existing files instead of overwriting, restores verbatim rule files (TDD.rules.md, git-commit-rules.md, CLAUDE-specific-fuckups.md) from canonical sources, and fills gaps from repo evidence like manifests, lockfiles, and CI workflows. - Verify-Then-Report Loop: Re-runs the full audit after repairs and produces a before → action → after report with every assumption recorded. - Use Case: A repo's AGENTS.md is a symlink and CLAUDE.md documents a test command that fails. The Skill detects both defects, replaces the symlink with a real file, fixes the phantom command row, and commits each repaired area separately. ## Quick Start Audit this repository's agent setup against the setting-up-a-project specification and repair any gaps you find.

Frequently Asked Questions about repairing-project-setup

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

FAQPage Schema
How do I fix a broken CLAUDE.md or AGENTS.md file?▼

Run an audit comparing the files against the canonical setting-up-a-project specification, then repair only the failing checks. Merge missing sections into existing content rather than rewriting, and restore verbatim rule files by copying from the canonical source.

How to detect drift in agent instruction files?▼

Check for unfilled {{PLACEHOLDER}} text, symlinked AGENTS.md files, missing required sections, and rule files that differ from their canonical templates using diff. Also verify that every documented command actually runs and that CLAUDE.md and AGENTS.md agree on commands and stack.

When should I repair setup instead of running full project setup again?▼

Repair when CLAUDE.md or AGENTS.md already exists, since those files record decisions worth preserving. Run the full setting-up-a-project interview only when no instruction files exist at all, because there is nothing to preserve and the interview matters.

Why is a symlinked AGENTS.md a problem for coding agents?▼

A symlinked AGENTS.md ships @ import syntax to agents that read it as dead text, since only Claude Code resolves those imports. The repair replaces the symlink with a real standalone file containing the required sections.

What happens if a documented command in CLAUDE.md fails?▼

A failing documented command is always treated as an audit failure. The fix either adds the missing script so the command works or removes the phantom row from the docs, whichever matches what the project actually has.