e4e81e4169daf899544e54081f033186267c4e25

Message

Add AGENTS.md cleanup skill

Diff

This diff is truncated to protect this page.

 1diff --git a/dot_agents/skills/agents-md-cleanup/SKILL.md b/dot_agents/skills/agents-md-cleanup/SKILL.md
 2new file mode 100644
 3index 0000000000000000000000000000000000000000..e98915be7a43cffdf6bbeae9f0fd4ec731268b30
 4--- /dev/null
 5+++ b/dot_agents/skills/agents-md-cleanup/SKILL.md
 6@@ -0,0 +1,66 @@
 7+---
 8+name: agents-md-cleanup
 9+description: Cleans and right-sizes repository AGENTS.md files. Use when an agent guide is too long, repetitive, overly detailed, or needs a concise repository map and development guidance.
10+disable-model-invocation: true
11+---
12+
13+# AGENTS.md cleanup
14+
15+Use this skill to make AGENTS.md a navigation and working guide, not a reference manual.
16+
17+## Workflow
18+
19+1. Find every `AGENTS.md` inside the target repository. Do not search parent directories or the whole home directory.
20+2. Read each file completely. Read its repository README and local instructions when you need to verify setup, test, release, or safety guidance.
21+3. Check `git status --short` before editing. Preserve user changes.
22+4. Check whether an AGENTS.md has generated-content markers or an auto-maintenance workflow. Preserve both unless the user asks to remove the automation.
23+5. Rewrite only the relevant AGENTS.md files. Use a target of 100–200 lines unless the user gives a different target.
24+6. Run `git diff --check`, verify the line count, and review the diff for lost safety constraints.
25+
26+## Keep
27+
28+Keep concise, stable information that helps an agent find the right place and work safely:
29+
30+- a one-paragraph repository purpose
31+- a package or module map at directory level
32+- setup, build, lint, test, and focused-test commands
33+- the usual path for an API or feature change
34+- migration, generated-code, secrets, deployment, and production-access constraints
35+- pointers to the source of truth: code, manifests, protobuf contracts, or README sections
36+
37+## Remove
38+
39+Remove information that an agent can find by reading the named file or package:
40+
41+- dependency and technology inventories
42+- file-by-file descriptions
43+- API request and response schemas
44+- database table schemas and domain edge cases
45+- implementation algorithms, cache settings, and internal call sequences
46+- code, logging, tracing, test, benchmark, and concurrency examples
47+- generic language advice and duplicate sections
48+- full environment-variable tables and step-by-step operational commands
49+- volatile deployment details such as image tags, ports, hostnames, or workflow internals
50+
51+## Operations and README
52+
53+Check whether the README already documents releases, rollbacks, production commands, breakglass access, and secrets procedures.
54+
55+- If the README covers an operational procedure, keep only a short safety rule and a pointer in AGENTS.md.
56+- If a critical procedure is absent from the README, do not remove its safety constraint from AGENTS.md. Add or propose concise README documentation when the task includes documentation changes.
57+- Never include credentials, secret values, or breakglass command lines in AGENTS.md.
58+
59+## Generated content
60+
61+For auto-maintained files, keep the maintenance notice and these markers:
62+
63+```markdown
64+<!-- AGENTS-MD:AUTO:START -->
65+<!-- AGENTS-MD:AUTO:END -->
66+```
67+
68+Put a persistent scope rule outside the generated region. State that the document must stay concise, give a line target, and must not become a reference manual. Direct durable procedures to the README.
69+
70+## Writing standard
71+