Analyze branch diffs and session transcripts to propose and commit retro changes.
npx skills add https://github.com/dev32-io/ccToolBox --skill retro-dev32-io
Please help me install this Agent Skill. Skill: retro Source: https://github.com/dev32-io/ccToolBox/tree/main/plugins/devTools/skills/retro Command: npx skills add https://github.com/dev32-io/ccToolBox --skill retro-dev32-io
This Skill enables teams to run a structured, end-to-end retrospective on a completed feature branch, distilling learnings, proposing concrete changes, and recording everything in a single, auditable commit.
Run the retro on your current feature branch to generate and commit retro artifacts in one go.
High-intent search queries and answers about installing and using this skill.
Automating a branch retrospective is done by analyzing the branch diff and session transcript to propose changes, then applying them in a single auditable commit. The process coordinates bootstrap, analysis, application, and commit phases end-to-end.
A feature branch retrospective distills learnings from a completed branch by analyzing diffs and transcripts to surface actionable improvements. It generates a candidate table of changes with evidence and destinations to enhance code quality and process hygiene.
Yes, you need git, jq, and mktemp installed to run automated retrospectives. These dependencies provide the deterministic inputs and temporary environments required for the scripts to analyze branches and commit artifacts.
Generating a candidate table of code changes from a git branch diff involves context-aware analysis of the diff alongside session transcripts. The retrospective process proposes concrete changes with evidence and destinations, requiring per-candidate approval before application.
Yes, you can review and approve individual improvements before committing retro artifacts. The workflow enforces explicit user intent by providing a per-candidate approval workflow for each proposed change generated from the branch analysis.
The best way to record learnings from a feature branch in a single commit is to use an automated retrospective process that applies approved changes and writes retro artifacts together as a single chore commit for traceability.
goffityAnalyze git changes to generate retrospective drafts with Before/After context.
abdullah1854Generate conventional commit messages from staged Git changes.
andrewblockernstAutomates code quality verification and rollback with Python scripts and Git integration.
miounet11Generate conventional commit messages from staged Git changes.
