keep-agents-and-readme-fresh
Keep Agents And README Fresh
Install the canonical Documentation Freshness policy into existing agent instruction files. This is an additive, one-time setup task.
Canonical Section
## Documentation Freshness
Repo reality is the source of truth. If `AGENTS.md` or `README.md` becomes false, update it in the same change when the fix is objective.
Objective facts include repo structure, tracked paths, setup commands, validation commands, runtime/tooling, skill/resource/prompt inventory, and workflow constraints proven by the repo.
- Update `AGENTS.md` when it is stale about agent-facing repo reality.
- Update `README.md` when it is stale about human-facing purpose, entry points, install, or use.
- Ask before changing policy, philosophy, positioning, or workflow intent.
- If both docs are stale, update both. Do not make them mirror each other unless the same fact belongs in both.
- Ignore temporary, generated, local-only, and unrelated untracked files.
- If unrelated user changes make docs look stale, ask before broadening scope.
More from cameronapak/jstack
unslop
Removes AI-generated code slop from a git branch diff. Cuts unnecessary comments, verbose patterns, and redundant code while preserving intent. Invoke when you want to clean up AI-generated code in a branch.
2christian-ai-creator-helper
Evaluate, build, or resource Christian AI applications. Covers the 5 unofficial rules for Christian AI apps, Bible developer resources (APIs, SDKs, MCP servers, concordance, commentary), guardrail implementation, and app testing. Use when building an AI tool for Christians, evaluating whether an AI app meets faith.tools standards, looking for Bible APIs or MCP servers, setting up Christian AI guardrails, or testing Christian AI chatbots.
2