Agent skill · software engineering · daymade
auto-repo-setup
Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator handoff. Use when a repo won't run, a teammate onboards, hook output duplicates, or commit/push/conflict needs guarding. Not for lost-commit recovery (use git-safety-net), GitHub ops (use github-ops), or history scrubbing (use github-sensitive-data-cleanup).
Why this skill is useful
Adds specific commands and workflows for diagnosing and repairing repository setups that the AI wouldn't reliably generate on its own.
What it needs
Requires git, python installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
Auto Repo Setup Make the repository usable without changing the user's normal way of working. Treat setup as an evidence-driven repository task, not as a special interface for people with a particular job title. Entry router Classify the request before changing anything. Do not combine modes merely because they all contain the word "setup". User outcome Mode First action --- --- --- "It won't run", missing dependency, new machine Environment repair Read project instructions and detect the actual stack "Sync before we work", "pull the latest", or a status question during repository maintenance Session routine Determine sync authority from the ongoing task and project instructions, then use Workflow B Repeated or unexpected hook output Hook diagnosis Count registrations and firing sessions before editing configuration A teammate needs a repeatable handoff Repository handoff Audit existing onboarding and fill only the missing operational contract Commit, push, conflict, leaked secret/history Git safety Read references/gitsafety.md before mutation Behavior must happen before the first prompt Startup automation Read references/startupautomation.md and pass its hook gate Operating principles 1. Do not infer competence from role. Match the user's demonstrated altitude. A collaborator can tell an agent "sync the remote first"; do not invent a launcher, shortcut, or wizard unless the user asked for one. 2. Use the least mechanism that satisfies the outcome. Prefer, in order: direct Agent instruction → project instruction → explicit command → lifecycle hook. A hook is not a more professional version of a sentence. 3. Inspect authority before producing. Read the current user request, then project instructions, onboarding/runbooks, manifests, lockfiles, and actual command output. Do not make ONBOARDING.md, Python, uv, ffmpeg, or .env mandatory for repositories that do not declare them. 4. Preserve user work. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/auto-repo-setup