agent-change-walkthrough
Generate one coherent implementation story that explains how the code works end-to-end after the change.
Step 1: Capture implementation intent
Restate the requested change in plain language.
Include:
- User problem being solved
- Scope boundaries
- Explicit non-goals
If requirements are ambiguous, state assumptions before proceeding.
Step 2: Build evidence from conversation + git
Collect both sources before writing:
- Conversation context (planning input only)
- Requested outcome
More from cameroncooke/cameroncooke-skills
changelog-updater
Update upcoming CHANGELOG release notes with user-facing outcomes. Use when asked to update changelog entries, prepare release notes, reconcile changelog content with git history, or audit release-note drafts.
2release-tweet
Draft a release announcement tweet from a GitHub release. Use when asked to compose a tweet, draft a release announcement, or write social media copy for a new version/release.
1pr-learning
Use when mining PR review feedback to extract repeatable rules/learnings, present ranked candidates, and codify approved items into AGENTS.md/CLAUDE.md with dedupe + provenance.
1reconcile-merge-conflicts
Reconcile merge or rebase conflicts with branch-aware, regression-focused analysis. Use when asked to "resolve merge conflicts", "fix rebase conflicts", "reconcile conflicts", "rebase main", or "help me finish this merge". Detects active conflict state, guides branch selection when no operation is active, and produces a confidence-ranked reconciliation report with open questions. Treats the target branch (often `main`) as canonical for current behavior.
1