Files
ai-training/.cursor/skills/refactor/templates/list-of-changes.md
T
Oleksandr Bezdieniezhnykh cdcd1f6ea7 Fix .cursor skills consistency: flow resolution, tracker-agnostic refs, report naming, error recovery
- Rewrite autopilot flow resolution to 4 deterministic rules based on source code + docs + state file presence
- Replace all hard-coded Jira references with tracker-agnostic terminology across 30+ files
- Move project-management.mdc to _project.md (project-specific, not portable with .cursor)
- Rename FINAL_implementation_report.md to context-dependent names (implementation_report_tests/features/refactor)
- Remove "acknowledged tech debt" option from test-run — failing tests must be fixed or removed
- Add debug/error recovery protocol to protocols.md
- Align directory paths: metrics -> 06_metrics/, add 05_security/, reviews/, 02_task_plans/ to README
- Add missing skills (test-spec, test-run, new-task, ui-design) to README
- Use language-appropriate comment syntax for Arrange/Act/Assert in coderule + testing rules
- Copy updated coderule.mdc to parent suite/.cursor/rules/
- Raise max task complexity from 5 to 8 points in decompose
- Skip test-spec Phase 4 (script generation) during planning context
- Document per-batch vs post-implement test run as intentional
- Add skill-internal state cross-check rule to state.md
2026-03-28 02:34:00 +02:00

1.7 KiB

List of Changes Template

Save as RUN_DIR/list-of-changes.md. Produced during Phase 1 (Discovery).


# List of Changes

**Run**: [NN-run-name]
**Mode**: [automatic | guided]
**Source**: [self-discovered | path/to/input-file.md]
**Date**: [YYYY-MM-DD]

## Summary

[1-2 sentence overview of what this refactoring run addresses]

## Changes

### C01: [Short Title]
- **File(s)**: [file paths, comma-separated]
- **Problem**: [what makes this problematic / untestable / coupled]
- **Change**: [what to do — behavioral description, not implementation steps]
- **Rationale**: [why this change is needed]
- **Risk**: [low | medium | high]
- **Dependencies**: [other change IDs this depends on, or "None"]

### C02: [Short Title]
- **File(s)**: [file paths]
- **Problem**: [description]
- **Change**: [description]
- **Rationale**: [description]
- **Risk**: [low | medium | high]
- **Dependencies**: [C01, or "None"]

Guidelines

  • Change IDs use format C## (C01, C02, ...) — sequential within the run
  • Each change should map to one atomic task (1-5 complexity points); split if larger
  • File(s) must reference actual files verified to exist in the codebase
  • Problem describes the current state, not the desired state
  • Change describes what the system should do differently — behavioral, not prescriptive
  • Dependencies reference other change IDs within this list; cross-run dependencies use tracker IDs
  • In guided mode, the input file entries are validated against actual code and enriched with file paths, risk, and dependencies before writing
  • In automatic mode, entries are derived from Phase 1 component analysis and Phase 2 research findings