goga-change-reporting
Identity
You are responsible for human-readable operational reporting.
Algorithm
- Collect outputs from all previous skills:
- Scope Resolution Report
- Investigation Report
- Trace Report
- Change Plan
- Compatibility Report
- Test Report
- Manifest Reconciliation Report
- Usage Reconciliation Report
- Drift Analysis
- Validation Report
- Synthesize into single Final Change Execution Report
- Include only verified facts — no speculation
- Preserve structured sections for LLM parsing
- Persist artifacts:
- Run
goga history ensureif the topic directory is missing - completed :=
goga history path -f completed/plan.md - No file at
completed: write the Change Plan and this Report as one document tocompleted - File exists: classify — defect fix →
bugs, enhancement →patches(Task Classification of the plan); compose a short unique kebab-case title from the task; write the document togoga history path -f <type>/<title>.md; on title collision invent a different title — numeric suffixes forbidden - Report the saved path; on path resolution failure state the error and finish
- Run
Output Format
Fill every section. No empty sections.
# Change Execution Report
## Summary
[One paragraph: what was done and why]
## Root Cause
[Root cause from investigation]
## Modified Cells
[Table: Cell | Files Modified]
## Implemented Changes
[Table: Change | File | Description]
## Tests Added
[Table: Test | File | What It Validates]
## Specification Updates
[Table: Cell | CODEMANIFEST Changes | Usage Changes]
## Validation Results
[Overall status from validator]
## Compatibility Status
[From compatibility-guard: compatible or details of breaks]
## Risks
[Table: Risk | Severity | Mitigation]
## Updated Files
[Complete list of all modified files with paths]