Repository navigation
docs/fork/agent-rules.md + fork-ci doc-check: general agent rules, once - #874
Conversation
docs/fork/agent-rules.md holds the agent rules that hold in every project and on every machine, each once with a one-line why. Machine and project facts stay in their own instruction files and config; review rules link to the review skill instead of being copied. fork-ci/actions/doc-check is a general port of a project's doc check: size budgets and a no-history rule for instruction files, broken relative links in changed Markdown, and no dated report files added. Budgets and patterns come from an optional project config read at the base commit, with defaults; a missing or empty config means the defaults, a broken one exits 2. Part of #834 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
lens: merge-path · reviewer: lens agent (A: public text, agent rules, doc-check fail-safe) · read at: 910dc3c |
Part of #834 (fork audit, G5).
What
docs/fork/agent-rules.md(about 6 KB): the general rules for coding agents, each written once with a one-line"why". Machine facts (capacity check, agent limits) and project facts (build slot, test servers, where owner
questions go) stay in the machine's or project's own instruction file and config. Review rules link to
fork-kit/review(see fork-kit/review: one general review skill; tiers, failure table, nit-only check and a drift test #845) and are not copied.fork-ci/actions/doc-check: a general port of a project's doc check, as a pinnable composite action.AGENTS.md,CLAUDE.md,SKILL.md, plus any the project adds) stay under a size budget;it warns above 90% and says when this change crossed the line.
skipped).
.github/doc-check.json, read at the base commit so a pull request cannot loosenits own rules. Missing, empty or
{}means the defaults; a broken config exits 2, never a pass.<path with spaces>),history patterns, the base-commit rule,
--all, and thatagent-rules.mditself passes and holds nothingpersonal.
FORK_CHANGES.mdand.github/fork-ci-tests.txtlist the new action.Rule summary
check && cmd, never piped); build slot + capped slice; stop what you started; guarded deletes; secrets only through their commandgit stash; fork stays off upstream; public repos hold nothing personal/tmp; post then read the link back; briefs via Write or<<'EOF'General vs project
is in the code or the doc.
.github/doc-check.json(extra instruction files such as anENGINEERING.md, its own budgets), itsAGENTS.mdfacts (build slot, test servers, owner-question repository,state file), the model-guard policy file and the review config. A project adopts doc-check by pinning the action
at a
ci/vNrelease; a follow-up trims each instruction file to its facts plus a link here.Not in this PR
🤖 Generated with Claude Code