tune-agent-docslisted

Reviews every markdown file in a repository that steers an AI coding agent — CLAUDE.md, AGENTS.md, GEMINI.md, `.cursor/rules/*.mdc`, `.clinerules`, `.windsurfrules`/`.windsurf/rules`, `.github/copilot-instructions.md`, Kiro's `.kiro/steering/*.md`, and similar — together as one corpus, then tightens them. Use whenever the user wants to audit, tune, reconcile, or clean up the instructions a repo gives its AI agents, or asks why an agent keeps missing or contradicting its own steering docs, or burning tokens on them — even when they only name one file, since the value is in reading it alongside its neighbors. Checks consistent terminology, leading-word front-loading, and each doc's token budget — size against its own format's stated limits, content loaded unconditionally that the harness could scope instead, guidance duplicated across multiple docs — applies the repo's own doc-authoring conventions where they hold generally, and calibrates each instruction's degrees of freedom to the fragility of what it govern
azborgonovo/ai-skills · ★ 0 · AI & Automation · score 75

Install: claude install-skill azborgonovo/ai-skills

# Tune Agent Docs A repo's AI-steering docs are read by whatever agent shows up, often several loaded into one context window at once — a root `CLAUDE.md` is rarely the only text an agent takes as instruction. When these docs disagree, use different words for the same thing, bury their point, or demand more rigor than the task needs, the agent pays that tax silently, on every run. This skill treats every steering doc in the repo as one corpus, combining review-skill's read-then-tighten mechanics with review-feature-suite's cross-file reconciliation. Work in two phases: **critique first, edit second**. Build the full picture, surface the findings, and only then touch a file. ## Find the corpus Use `Glob` for the conventions each harness actually recognizes today — see `references/steering-formats.md` for the current list and each format's own frontmatter and inclusion rules: `CLAUDE.md` and `CLAUDE.local.md` (including nested per-directory copies and `.claude/rules/**/*.md`), `AGENTS.md`, `GEMINI.md`, `.cursor/rules/**/*.mdc`, `.cursorrules`, `.clinerules` or `.clinerules/**/*.md`, `.windsurfrules` or `.windsurf/rules/**/*.md`, `.devin/rules/**/*.md`, `.github/copilot-instructions.md`, `.github/instructions/**/*.instructions.md`, `.kiro/steering/**/*.md`. Include the local/gitignored variant alongside its checked-in counterpart wherever a harness has one — that pairing is a common duplication site, not a reason to skip either file. Then follow every pointer a doc already