← ClaudeAtlas

gitflowlisted

End-to-end GitHub delivery workflow: inventory changes, create a conventional feature branch, make atomic commits per file/area with descriptive messages, validate (tests/lint/typecheck/build), push, open a pull request with a full body, review, merge to main, delete the branch, sync local main, and manage GitHub Projects tasks (create, assign, mark complete). Use when the user asks to commit changes, create a PR, merge to main, run a release workflow, make the git history look professional, or set up/complete GitHub Projects tasks.
Tash000/git-workflow-skill · ★ 1 · Code & Development · score 54
Install: claude install-skill Tash000/git-workflow-skill
# Git Release Workflow Ship a feature the professional way: a clean branch, atomic commits that tell a story, a reviewable PR, a clean merge, and a GitHub Projects trail that shows tasks were created, claimed, and completed. ## Principles - **Works solo AND in teams.** In a personal repo the agent may run the full cycle; in a company repo it obeys branch protection — it never bypasses required reviews, required checks, or CODEOWNERS, and never merges a PR that the repo's rules don't allow. It CANNOT override GitHub's own protections. - **One PR = one feature/fix.** Never bundle unrelated work into a single PR. - **Atomic commits.** Each commit is one logical unit (backend, frontend, tests, docs, config) and must leave the tree buildable. - **Commits tell the story.** The history should read like a changelog: a reader can see exactly what changed in each file and why. - **Never merge broken code.** CI green, tests green, lint/typecheck clean, and build succeeds — or no merge. - **Ask before destructive actions.** Anything with `force`, `reset --hard`, `branch -D` on a shared branch, or touching `main` directly requires explicit user confirmation. ## Workflow ### Phase 0 — Inventory & plan (always first) 1. Check what changed and where: ```bash git status --short git diff --stat | tail -20 ``` 2. Group the changes into **logical units** — derive the groups from the ACTUAL changed paths (`git status --short`), not a template. Typical groups