fix(refactor-plan): expand skill description and instructions#1676
Merged
aaronpowell merged 1 commit intoMay 11, 2026
Merged
Conversation
Clarify when to invoke the skill and require a plan-first, confirm-before-edit workflow so agents do not start changing files during planning.
Contributor
|
🔴 Contributor Reputation Check: HIGH risk
Maintainers: please review this contributor before merging. |
Contributor
🔍 Skill Validator Results✅ All checks passed
Summary
Full validator output```text Found 1 skill(s) [refactor-plan] 📊 refactor-plan: 520 BPE tokens [chars/4: 573] (detailed ✓), 14 sections, 1 code blocks ✅ All checks passed (1 skill(s)) ``` |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the existing refactor-plan skill to make it safer and more explicit for multi-file refactors by enforcing an investigate → plan → confirm workflow (i.e., plan-first and no edits during planning), and aligns the skills index entry to match the updated skill description.
Changes:
- Expanded the
refactor-planskill description to clarify when to use it and to require investigation and confirmation-before-editing. - Strengthened the skill instructions to prohibit edits during planning, require explicit scoping/dependency analysis, and require phased verification plus rollback/recovery guidance.
- Updated
docs/README.skills.mdto reflect the newrefactor-plandescription.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| skills/refactor-plan/SKILL.md | Clarifies and tightens the skill’s plan-first workflow, emphasizing investigation, sequencing, verification, rollback, and confirmation before implementation. |
| docs/README.skills.md | Updates the skills index entry so refactor-plan’s description matches the revised skill behavior. |
aaronpowell
approved these changes
May 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clarify when to invoke the skill and require a plan-first,
confirm-before-edit workflow so agents do not start changing
files during planning.
Pull Request Checklist
npm startand verified thatREADME.mdis up to date.stagedbranch for this pull request.Description
Updates the
refactor-planskill to make its behavior clearer and safer for multi-file refactors.Type of Contribution
Additional Notes
boundaries, and hidden coupling.
before implementation.
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.