← ClaudeAtlas

dev-github-hygienelisted

Ensures every change follows clean practices: proper branches, clear commit messages, documented env vars in .env.local (never create .env.example files), and engineering notes for each change. Use at the start of any feature to keep the repository organized and auditable.
talentedgeai/infinite-leverage · ★ 0 · Code & Development · score 60
Install: claude install-skill talentedgeai/infinite-leverage
# Developer: GitHub Hygiene ## Git Discipline - Run `git status` before any file work. Stop and report if uncommitted changes or merge conflicts. - Never force-push to any branch. Never skip hooks with `--no-verify`. - Never amend a commit that has been pushed to remote. - Never use `git add .` or `git add -A` — stage files explicitly by name. - Never create a commit unless explicitly instructed. ## Branch Convention - Sync with main first: `git checkout main && git pull origin main` - Create branch: `git checkout -b feat/{kebab-case-task-slug}` - Never push directly to `main` or `master` ## PR Convention - Title: `[type]: [concise description]` - Body: "Closes [plan item]. QA: all tests green." - Base branch is `main` - Squash merge to main. Delete branch after merge. ## .env.local Management `website/.env.local` (gitignored) is the ONLY env file. Never create a `.env.example` — it confuses agents and users. - If the task introduces new env vars: add them to `.env.local` with a one-line comment saying what they're for and where the value comes from - Collect real values just-in-time via `~/.claude/skills/infiniteleverage-init/scripts/collect-credentials.py` (merge-safe) - Never commit `.env.local` or any file containing real values ## Engineering Doc Scaffolding For each task, create: ``` docs/engineering/changes/{YYYY-MM}/{YYYY-MM-DD-{task-slug}}/ ├── TECH-PLAN.md ← before writing code ├── EXEC-PLAN.md ← phase checklist, check off live ├── CHANGELOG.md ← after