cc-fix

Route bug reports through validation, risk assessment, implementation, testing, and review.

Updated May 7, 2026
One-click install
npx skills add https://github.com/lgzarturo/codeconductor --skill cc-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-fix
Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/cc-fix
Command: npx skills add https://github.com/lgzarturo/codeconductor --skill cc-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a structured bug-fix workflow, enabling risk-aware routing and thorough validation from issue intake to resolution.

Core Features & Use Cases

  • Risk-based routing of bug reports to appropriate roles (Task Coach, Architect, Implementer, Tester, Reviewer)
  • Stepwise task cards, validation, implementation, regression testing, and documentation
  • Clear escalation and traceability to ensure quality and reproducibility

Quick Start

Provide a bug report and initiate the workflow to triage and fix the issue.

Frequently Asked Questions about cc-fix

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

FAQPage Schema
How do I automate a bug-fix workflow with risk assessment and regression testing?

You can automate a bug-fix workflow by routing tasks through validation, risk assessment, implementation, regression testing, and optional review to ensure thorough and reproducible issue resolution.

What is risk-based routing in software bug resolution?

Risk-based routing assigns bug reports to appropriate roles like Task Coach, Architect, Implementer, Tester, or Reviewer based on the assessed risk level and reported reproduction steps.

How do I structure bug reports for risk-aware triage and implementation?

To enable risk-aware triage, bug reports should include clear reproduction steps and risk levels to support accurate task-card generation and routing decisions.

Does this bug-fix workflow generate documentation artifacts for traceability?

Yes, the workflow produces stepwise task cards and documentation artifacts throughout the process to ensure clear escalation, traceability, and quality control from issue intake to resolution.

Can I use this bug-fix workflow for software development projects without external dependencies?

Yes, it operates independently without external dependencies and applies to software development projects where bugs are reported with reproduction steps and risk levels for end-to-end resolution.