wp-github-flow

# GitHub Contribution Flow > **Model note:** Issue-driven mode (root-cause tracing + fix) requires `sonnet` or `opus`. Changes-driven mode (group + commit existing edits) is mechanical and works well on `haiku`. ## Overview Two entry modes that converge on the same shipping flow (branch → scoped commits → push → PR): - **Issue-driven** — fetch issue → trace root cause → fix → ship. Wraps `superpowers:systematic-debugging`. Root cause MUST be confirmed before any fix is written. - **Changes-driven** — read the working tree → group changes by conventional-commit scope → one commit per scope → ship. No issue required. Both end at **§6 Branch, Commit, PR**, which is shared. ## When to use **Issue-driven:** - User says "analyze/debug/fix/investigate issue #NNN" - User pastes a GitHub issue URL and asks to debug it - User says "find the root cause of this bug" with an issue reference **Changes-driven:** - "commit my changes", "commit these scope by scope", "commit by scope" - "create a branch and PR", "open a PR for these changes" - "read all changes from X and commit + create PR" - Any request whose end goal is commits/branch/PR from existing working-tree edits **Not for:** Plugin version releases or WP.org SVN deploy — use `wp-plugin-release` and `wp-org-submission`. QA failure triage on an already-open PR — use `wp-ci-qa`. ## Required Sub-Skill **Issue-driven only:** Invoke `superpowers:systematic-debugging` before any fix. Do NOT skip Phase 1 (root cause investigatio...