andybaran

issue-driven-github-flow

Enforces an issue-driven GitHub Flow with multi-agent planning. Use this skill when the user wants to START or CARRY OUT development work in a git repository — implement a feature, fix a bug, make or change code, kick off a new project, or open/land a PR — including when they don't say "issue", "branch", or "gitflow" (e.g. "let's build X", "fix this bug", "add a feature", "start on Y", "get this project going"). It guarantees every change traces to a GitHub issue, gets a reviewed-and-approved plan before any code is written, lands on a `type/description` branch via a squash-merged PR with Conventional Commits, and never edits `main` directly. Do NOT trigger for purely informational or read-only requests that change nothing — e.g. "what's the git command for X", "explain this function", "show me the diff", "what branch am I on" — just answer those directly.