edkuksa/skills
1
0
Fork 0
mirror of https://github.com/mattpocock/skills.git synced 2026-07-29 02:52:42 +07:00
Code Issues Packages Projects Releases Wiki Activity

to-issues: split into Process + Reference tiers

Browse Source 
Revert the description change and keep the wide-refactor material in
one place. Reshape the skill into a lean Process (steps) and a
Reference section holding the vertical-slice rules, the wide-refactor
expand–contract rules, and the issue body template as co-located
blocks the steps point to.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-07-07 16:35:39 +01:00
co-authored by Claude Opus 4.8
parent a0329ba957
commit aa591116bf
3 changed files with 26 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.changeset/to-issues-wide-refactor.md
+1 -1
View File
@@ -2,4 +2,4 @@
"mattpocock-skills": minor
---
Teach the **`to-issues`** skill to handle a **wide refactor** — a single mechanical change (like renaming a column) whose **blast radius** fans across the whole codebase, breaking thousands of call sites at once so no vertical slice can land green. The skill now spots this while exploring and slices it as **expand–contract** — expand the new form beside the old, migrate call sites in batches sized by blast radius, then contract the old form away — keeping CI green batch to batch (or, when it can't, only at a final integrate-and-verify issue). The leading words are seeded across the description, the explore step, and the drafting step.
Split the **`to-issues`** skill into a lean **Process** and a **Reference** section, and teach it to handle a **wide refactor** — a single mechanical change (like renaming a column) whose **blast radius** fans across the whole codebase, breaking thousands of call sites at once so no vertical slice can land green. The drafting step now points at two co-located reference blocks: the **Vertical slice rules** for ordinary tracer bullets, and **Wide refactors**, which slices the change by **expand–contract** (expand the new form beside the old, migrate call sites in batches sized by blast radius, then contract the old form away) so CI stays green batch to batch — or, when it can't, only at a final integrate-and-verify issue. The issue body template moves into Reference too.