repokit

Use repokit's setup mode, which diffs repo settings against a canonical map (merge-commit-only, delete-branch-on-merge, secret scanning), scaffolds missing baseline files like LICENSE, README, .gitignore, and AGENTS.md, then runs the about and labels modes. Every change is previewed and approved before applying.

The about mode reads your README and project manifest (package.json, pyproject.toml, Cargo.toml, and similar) to infer a one-line description and a focused topic set. It shows current versus proposed values per field and applies only what you approve via gh repo edit.

Yes. The labels mode checks for existing schemes in each namespace (lifecycle, priority, automation) before diffing, and offers to map onto your current labels instead of adding a parallel set. Labels outside the canonical sets are never deleted unless you explicitly ask.

Only the docs mode works locally, since it renames files using git history and never calls GitHub. The about, labels, and setup modes require an authenticated gh CLI and an existing GitHub remote; without shell access, the skill prints the exact gh commands for you to run.

repokit deliberately leaves scaffold files unstaged and docs renames staged so a commit skill or the user controls grouping and commit messages. This separation keeps repository configuration auditable and avoids mixing setup changes into unrelated commits.

The docs mode assigns a zero-padded serial prefix to each dated artifact under docs/, ordered by filename date, git add time, or filesystem mtime. It previews the renames per directory, uses git mv for recoverability, and repairs all in-repo references to old paths.