Auto Repo Setup & Git Safety
Diagnoses and repairs repos that won't run, then standardizes onboarding docs and guarded commit/push/history workflows.
Dev & CodingIntermediate★ 1,419⑂ 219AI score 9/10Last updated: Sep 22, 2026
What it does
- Entry router: classifies your request into one of six modes (environment repair, session sync, hook diagnosis, repository handoff, Git safety, startup automation) so it only does the relevant work.
- Evidence-first, read-only diagnosis: reads AGENTS.md/CLAUDE.md, onboarding/runbooks, README, manifests, lockfiles and CI, then runs
scripts/check_env.pyto check only the toolchains your project actually declares — no installs, no printing secret values. - Smallest viable repair: captures the exact command, exit code and output, traces the failure to its declaring source, applies a minimal project-consistent fix, and re-verifies with the project's real smoke test.
- Protects your work: never auto-stashes, merges, rebases, force-pushes or discards local changes just to make setup look green.
- Git safety gates: reference docs must be read before commit, push, conflict resolution or history rewrite; public push, force push and rewrites require explicit approval, and leaked credentials must be revoked.
Who it's for
- Developers onboarding onto a new machine or repo that simply won't start
- Leads who need a repeatable ONBOARDING.md handoff for teammates
- Anyone debugging duplicated SessionStart hook output or auditing project instructions/hooks
- Anyone who committed a secret and wants a cautious history-cleanup path
Examples
- "The dev server won't start" → manifest-based inventory → install only the one missing toolchain → run the documented smoke test and report evidence, changes and verification.
- "Sync the latest remote before we work" → inspect branch/upstream/working tree →
git pull --ff-onlywhen clean; explain (never auto-merge) when local changes or diverged histories exist. - "My startup notice prints three times" → enumerate project/local/user/managed/plugin hook registrations, count them, identify which sessions fired, and state the root cause before editing config.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/daymade/claude-code-skills/HEAD/auto-repo-setup/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the auto-repo-setup folder from the GitHub repo daymade/claude-code-skills into my ~/.claude/skills/auto-repo-setup/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/daymade/claude-code-skills.git && cp -r claude-code-skills/auto-repo-setup ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal.
- Clone the repository:
git clone https://github.com/daymade/claude-code-skills.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy the skill:
cp -r claude-code-skills/auto-repo-setup ~/.claude/skills/ - Confirm the bundled
scripts/andreferences/folders came along. - To use the helper scripts, install Python 3.10+ and
uv(manual inspection still works without them). - Restart Claude Code and try: "Diagnose why this repository won't run."
View source on GitHub ↗License: MIT