Auto Repo Setup

What it does

• Environment repair: reads AGENTS.md, CLAUDE.md, onboarding docs, README, manifests and lockfiles in order to detect the real stack, then runs a read-only inventory via scripts/check_env.py and fixes only the smallest project-consistent gap.
• Session sync routine: handles "pull the latest before we work" safely — never auto-stashes, merges, rebases or force-pushes to make setup look green.
• Hook diagnosis: when SessionStart output is duplicated, it enumerates project/local/user/managed/plugin registrations and states the root cause before editing config.
• Repository handoff: uses an onboarding template as a checklist to produce docs with real commands, expected output, and recovery steps.
• Git safety gates: reads safety references before commit, push, conflict resolution, or history rewrite; public push, force push, and rewrites require explicit approval.

Who it's for

• Developers on a new machine or fresh clone where nothing runs
• Team leads tired of answering the same setup questions
• Claude Code users with duplicated or unexpected startup hook output
• Maintainers auditing leaked credentials or PII before public release

Example uses

1. "The dev server won't start" → traces the failure to the declaring manifest, applies the minimal fix, and re-runs the project's real smoke test to verify.
2. Onboarding a teammate → audits existing docs, fills only the missing operational contract in ONBOARDING.md, with expected output per command.
3. Startup message printed three times → counts actual registrations instead of guessing, then previews cleanup with --dry-run before applying.

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.