Context
After the develop → pr-review → merge cycle completes, no learnings are captured. The cycle ends silently.
Proposal
After pr-review results in an approval, append a brief "lessons learned" section to the issue comment:
- What went well (e.g., test coverage, clean implementation)
- What was harder than expected (e.g., unexpected dependencies, edge cases found during review)
- Patterns worth reusing (e.g., approach to testing, API design decisions)
This could be added to the REVIEWPR_AGENT_PROMPT as an additional instruction: "If approving, include a brief 'Lessons Learned' section noting what went well and what was harder than expected."
Rationale
This is a lightweight version of the "reflect" phase found in structured development methodologies:
Even without automated learning, capturing lessons on the issue provides value for human retrospectives and future reference.
Priority
Low — this is a nice-to-have improvement, not critical to the workflow.
Context
After the develop → pr-review → merge cycle completes, no learnings are captured. The cycle ends silently.
Proposal
After
pr-reviewresults in an approval, append a brief "lessons learned" section to the issue comment:This could be added to the
REVIEWPR_AGENT_PROMPTas an additional instruction: "If approving, include a brief 'Lessons Learned' section noting what went well and what was harder than expected."Rationale
This is a lightweight version of the "reflect" phase found in structured development methodologies:
/retro(retrospective)Even without automated learning, capturing lessons on the issue provides value for human retrospectives and future reference.
Priority
Low — this is a nice-to-have improvement, not critical to the workflow.