Repository navigation
v1.2.1 · Branch protection and CLAUDE.md retirement
Added
setup-snappedly-skillsrecommends protecting the base branch so every change arrives through a merged PR. The rule blocks direct pushes and force pushes for everyone, administrators included, and requires no approving review, so agents can still merge PRs. Setup applies it through the code host's API when it has admin access, or gives you the settings to apply, then reads the rule back and records it indocs/agents/code-host.md.
Changed
setup-snappedly-skillsrecommends retiring each repositoryCLAUDE.md. Claude Code readsAGENTS.mdonly when noCLAUDE.mdexists, so a leftoverCLAUDE.mdhid theAGENTS.mdthat setup writes. Setup moves each ruleAGENTS.mdlacks into theAGENTS.mdat the same directory, puts Claude-specific rules in.claude/rules/, and asks about conflicting rules. When a teammate's Claude Code cannot readAGENTS.mddirectly, setup proposes aCLAUDE.mdthat only importsAGENTS.mdinstead.
Updating existing repositories
Rerun setup-snappedly-skills to review base branch protection and migrate an existing CLAUDE.md. Setup keeps existing branch rules, flags any that would block an agent merge, and records a declined rule with its reason so later runs do not ask again.
For CLAUDE.md, setup shows where each rule goes and removes the file only when you agree. If you keep it, setup adds an AGENTS.md import and records your reason in the file so later runs do not ask again while it holds.
Update the installed skills with npx skills update, then rerun setup-snappedly-skills in each repository.