rai-bugfix-review

Perform bugfix retrospectives and extract actionable patterns into retro.md and patterns.jsonl.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-bugfix-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-bugfix-review
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-bugfix-review
Command: npx skills add https://github.com/humansys/raise --skill rai-bugfix-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to perform a structured retrospective on bugfixes, extract actionable patterns, and drive process improvements to prevent repeat issues.

Core Features & Use Cases

  • Retrospective analysis of bugfix work to capture root causes and learnings.
  • Pattern extraction and linkage to the knowledge graph for ongoing governance.
  • Guidance for next steps in the bugfix lifecycle (pattern reinforcement, next skill triggers).

Quick Start

Run the bugfix review workflow for a completed bugfix to generate a retrospective and update patterns and governance artifacts.

Frequently Asked Questions about rai-bugfix-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a retrospective on bugfix work to capture root causes?

A bugfix retrospective captures root causes and organizational learnings by reviewing completed fixes, generating a retro.md artifact, and extracting actionable patterns to prevent repeat issues in future development cycles.

What is the best way to extract actionable patterns from bugfixes?

Extracting actionable patterns from bugfixes involves analyzing completed fixes to identify systemic issues, then documenting these learnings in a patterns.jsonl governance file linked to the knowledge graph for traceability.

How does bugfix pattern extraction link to a knowledge graph for governance?

Pattern extraction links to the knowledge graph by updating governance data through a patterns.jsonl file during the post-fix workflow, ensuring each documented learning is traceable for ongoing process improvement.

When do I need to generate retrospective artifacts in the bugfix lifecycle?

Retrospective artifacts are generated during the post-fix phase of the bugfix lifecycle, producing a retro.md file and updating governance data to ensure traceability and drive process improvements before closing the issue.

Can I use this bugfix review workflow without prior dependencies?

The bugfix review workflow operates without prior dependencies, functioning independently to analyze completed fixes, extract patterns, and generate retrospective artifacts for process improvement.