Squashed 'docs/standards/playbook/' changes from c3f8137..25d895d
25d895d 🐛 fix(gitea_workflow): clean up temp repos after job steps 2bc3b11 🐛 fix(gitea_workflow): clean up temporary repo dirs in workflows 98c3f30 📝 docs(agent_rules): allow plan execution on current branch 16c7230 📝 docs(prompts): define custom verify layering 8efc4dd 🐛 fix(skills): quote commit-message description bc8498f 🐛 fix(ci): install tomli for gitea tests 55cda3b 🐛 fix(tests): report missing toml parser clearly c0729c7 🐛 fix(playbook): import Optional for cli compatibility 63e24bf 📦 deps(skills): sync thirdparty skills d2f9356 🐛 fix(ci): isolate gitea workflow repos 588b81d 🐛 fix(ci): inline gitea workflow bootstrap e0b1c3a ♻️ refactor(skills): standardize first-party skill contracts 2c5050d ♻️ refactor(skills): rename repo skills source dir f049dfb 📦 deps(skills): drop duplicate first-party superpowers skills 234b335 ✨ feat(workflow): add superpowers planning and execution state tracking c1702a6 📝 docs(markdown): format tracked markdown and drop stale templates 2325409 📝 docs(markdown): clarify optional markdownlint usage 214c44e 🔧 chore(markdown): add markdownlint baseline and lint fixes a22b324 📝 docs(templates): add execution and memory-bank prompt templates 223a797 📝 docs(templates): update README for Claude Code and current features 4ac8672 📝 docs: simplify README + platform-agnostic tools + auto-create local rules 2431c9d 📝 docs: add claude_md config and use cross-platform paths d64b248 📝 docs: fix README.md inaccuracies and add Claude Code info c8d6bf2 🐛 fix(playbook): use relative paths in CLAUDE.md when not at project root 6518f0f ✨ feat(playbook): auto-create CLAUDE.md with path discovery 6ec9a45 ✨ feat(skills): add skill_link symlink support + platform-agnostic prompt 9f8b6b5 📝 docs: update README and config example for Claude Code support 79cff6c 📝 docs(skills): add Claude Code platform support 452c6f5 ✨ feat(playbook): auto-inject AGENTS.md into CLAUDE.md e1dbf3c 🐛 fix(skills): remove dual-path from commit-message skill f3a7259 🔧 chore(ci): use prepare_repo.sh in both workflows da08212 🔧 chore(ci): extract prepare_repo.sh and clean up workflows 7ade85e 🗑️ remove(tsl): drop syntax_book/, data/ source and build script f94dba0 ♻️ refactor(skills): update playbook.py and tests for thirdparty/ layout b3df412 ♻️ refactor(skills): separate thirdparty skills into thirdparty/ subdirectory 64950e7 📦 deps(skills): sync thirdparty skills a2e3cb0 ✨ feat(playbook): add no_backup deploy controls 8609d59 🐛 fix(docs): repair reference catalog source links 956da11 🐛 fix(playbook): publish hidden ci test fixes 3f67754 📦 deps(skills): sync thirdparty skills 08ca87b 📦 deps(skills): add karpathy thirdparty sync 96b705b 📝 docs(tsl): rebuild canonical syntax and routing manual 3ed5052 📦 deps(skills): sync thirdparty skills 60108dd 📦 deps(skills): sync thirdparty skills da85d4e 🐛 fix(thirdparty): prune nested project snapshots a2a697e 📦 deps(skills): sync thirdparty skills 9df610a 🐛 fix(thirdparty): exclude duplicated superpowers skills 33dd5bb 🐛 fix(thirdparty): preserve optional manifest fields 91b0ea7 🐛 fix(thirdparty): preserve manifest during snapshot update 2e26f98 🔧 chore(thirdparty): generalize skills sync pipeline 5b9c1e3 📦 deps(skills): sync superpowers 2f2d34a 📝 docs(readme): normalize subtree command spacing 62db7db 🐛 fix(ci): serialize superpowers update and sync 3463223 🐛 fix(ci): use literal superpowers sync paths 48f6de8 📦 deps(skills): sync superpowers 4b23529 🔧 chore(ci): merge superpowers update and sync workflow a56d75b 📦 deps(skills): sync superpowers 84bcefa 🔧 chore(ci): use ci[bot] commit author name 00a07e5 📦 deps(skills): sync superpowers 7b84daf 🐛 fix(templates): enforce main loop progress tracking 51373d7 🔧 chore(ci): automate superpowers sync workflow eaaa39c 🐛 fix(ci): prevent stale superpowers sync from restoring skills block 79755c6 📦 deps(skills): sync superpowers 836d878 📦 deps(skills): sync superpowers 8216c9f 📦 deps(skills): sync superpowers 9439505 🐛 fix(playbook): address reported repo issues git-subtree-dir: docs/standards/playbook git-subtree-split: 25d895d8b3f56624ccfe99ad7289e9eb49e0f316
This commit is contained in:
@@ -0,0 +1,109 @@
|
||||
---
|
||||
name: bulk-refactor-workflow
|
||||
description: Use when renaming symbols, migrating APIs, or applying safe mechanical changes across many files in the repository.
|
||||
---
|
||||
|
||||
# Bulk Refactor Workflow（批量重构 / 大范围修改）
|
||||
|
||||
## Overview
|
||||
|
||||
Guide repository-wide mechanical edits without losing scope control or damaging
|
||||
unrelated work. Core principle: enumerate first, transform mechanically, verify
|
||||
in loops, and keep every batch auditable.
|
||||
|
||||
## When to Use
|
||||
|
||||
- Rename APIs, symbols, file conventions, or repeated string patterns
|
||||
- Apply scripted or structural edits across many files
|
||||
- Migrate callers to a new interface where the change pattern is repeatable
|
||||
|
||||
## When Not to Use
|
||||
|
||||
- One-off logic changes where no repeatable transformation exists
|
||||
- Exploratory redesign or feature work that needs new architecture decisions
|
||||
- Cleanup that is only formatting/lint alignment; use `style-cleanup` directly
|
||||
|
||||
## Inputs
|
||||
|
||||
- Scope: directories, file types, include/exclude rules
|
||||
- Transformation: rename, replace, codemod, scripted edit, migration strategy
|
||||
- Constraints: behavior-preserving vs. compatibility window vs. staged rollout
|
||||
- Verification commands: smallest useful loop plus final gate
|
||||
|
||||
## Procedure
|
||||
|
||||
1. **Baseline and bound the scope**
|
||||
|
||||
- Record `git status --short`.
|
||||
- Dirty worktrees are allowed.
|
||||
- Do not revert unrelated changes.
|
||||
- Mark the exact target file set before editing.
|
||||
- Run a baseline verification command so existing failures are not misattributed
|
||||
to the refactor.
|
||||
|
||||
2. **Enumerate every intended hit**
|
||||
|
||||
- Search before editing with `rg`, `git grep`, or a structured query.
|
||||
- Separate real code hits from comments, docs, generated files, and samples.
|
||||
- Write down exclusions before running the transformation.
|
||||
|
||||
3. **Choose the safest mechanical transform**
|
||||
|
||||
- Prefer deterministic transforms: codemods, scripts, structured edits, or
|
||||
narrow search/replace with explicit scope.
|
||||
- If compatibility matters, use a staged migration: adapt providers first,
|
||||
migrate callers second, remove compatibility layer last.
|
||||
|
||||
4. **Apply in bounded batches**
|
||||
|
||||
- First, apply the transformation in bounded batches.
|
||||
- Verify each batch before widening scope.
|
||||
- Stop immediately if output differs from the expected hit class.
|
||||
|
||||
5. **Verify in loops**
|
||||
|
||||
- Run the smallest relevant verification after each batch.
|
||||
- Re-check the hit list after edits to confirm the intended pattern is gone and
|
||||
unintended patterns were not introduced.
|
||||
|
||||
6. **Finish with targeted cleanup**
|
||||
|
||||
- If the mechanical change leaves formatting or lint fallout, Use `style-cleanup` for the final formatting/lint pass.
|
||||
- Keep that cleanup scoped to the refactor set unless the user approves a wider
|
||||
pass.
|
||||
|
||||
7. **Report**
|
||||
|
||||
- Summarize files touched, transform rules used, verification evidence, and any
|
||||
residual risk.
|
||||
|
||||
## Output Contract
|
||||
|
||||
- `Scope:` files, directories, and exclusions actually used
|
||||
- `Transformation:` exact rule or script applied
|
||||
- `Batches:` how the work was partitioned
|
||||
- `Verification:` commands, exit status, and what each loop proved
|
||||
- `Risks:` remaining ambiguous areas, compatibility debt, or deferred cleanup
|
||||
|
||||
## Success Criteria
|
||||
|
||||
- Every changed file belongs to the declared scope
|
||||
- The transformation is reproducible and explainable
|
||||
- Verification passes at both batch level and final gate
|
||||
- Unrelated work in the repository is preserved
|
||||
|
||||
## Failure Handling
|
||||
|
||||
- If the hit list is ambiguous, stop and refine scope before editing
|
||||
- If the transform cannot be expressed mechanically, downgrade to a normal
|
||||
refactor plan instead of pretending it is safe bulk work
|
||||
- If verification fails mid-batch, stop, inspect the smallest failing delta, and
|
||||
correct the transform before continuing
|
||||
- If compatibility risk is higher than expected, split the migration into staged
|
||||
commits or phases
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Never run repository-wide replacement without an explicit hit review
|
||||
- Never mix unrelated cleanup into the same batch
|
||||
- Never hide a large-scope behavior change behind the label "mechanical refactor"
|
||||
Reference in New Issue
Block a user