fix — community CMIDCABot, community, ide skills

v1.0.0
GitHub

About this Skill

Ideal for Code Review Agents needing automated issue resolution and efficient developer workflow integration. Fix issues from code review. Use when the user invokes /fix or asks to address review findings for an issue.

arttttt arttttt
[0]
[0]
Updated: 3/6/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
36
Canonical Locale
en
Detected Body Locale
en

Ideal for Code Review Agents needing automated issue resolution and efficient developer workflow integration. Fix issues from code review. Use when the user invokes /fix or asks to address review findings for an issue.

Core Value

Empowers agents to automate code review fixes following specific developer behavior profiles and conventions outlined in CLAUDE.md and ARCHITECTURE.md, utilizing protocols like explicit approval for fix implementation and commit/push operations.

Ideal Agent Persona

Ideal for Code Review Agents needing automated issue resolution and efficient developer workflow integration.

↓ Capabilities Granted for fix

Automating code review fixes
Generating fix plans based on review findings
Implementing approved fixes and committing changes

! Prerequisites & Limits

  • Requires access to review findings and codebase
  • Must follow specific developer behavior profiles and conventions

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is fix?

Ideal for Code Review Agents needing automated issue resolution and efficient developer workflow integration. Fix issues from code review. Use when the user invokes /fix or asks to address review findings for an issue.

How do I install fix?

Run the command: npx killer-skills add arttttt/CMIDCABot/fix. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for fix?

Key use cases include: Automating code review fixes, Generating fix plans based on review findings, Implementing approved fixes and committing changes.

Which IDEs are compatible with fix?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for fix?

Requires access to review findings and codebase. Must follow specific developer behavior profiles and conventions.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add arttttt/CMIDCABot/fix. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use fix immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

fix

Install fix, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Fix Command

Behavior Profile

Use the developer skill as the behavior profile for this command. Treat its rules as mandatory.

Follow CLAUDE.md, conventions.md, and ARCHITECTURE.md.

Task

Fix issues identified in code review.

Interaction Contract

  1. Fetch review findings.
  2. Produce a fix plan.
  3. Wait for explicit approval.
  4. Implement fixes, commit, push.

Algorithm

Step 1: Get findings

  • If ID missing → ask "Which issue to fix?"
  • Normalize ID: add DCATgBot- prefix if missing
  • Use beads to get issue details + comments
  • If no review comments: report "No review findings. Run /review first."
  • Parse findings (Critical, Should Fix, Consider)

Step 2: Create fix plan

Show plan only; do not implement yet.

## Fix Plan
<plan>
---
Confirm? (ok / changes)

Step 3: On approval

  • Implement fixes per plan
  • Commit: fix(<scope>): address review findings
  • Push to remote

Step 4: Report

Fixes complete for <id>.
Fixed: [C1], [S1]...
Next: /review <id>

Plan Format

markdown
1## Fix Plan
2
3**Issue:** <id> - <title>
4**Branch:** <current>
5
6**Findings to fix:**
7- [C1] Title - approach
8- [S1] Title - approach
9
10**Deferred:**
11- [N1] Title - reason

Severity Handling

SeverityDefault
CriticalAlways fix
Should FixFix by default
ConsiderSuggest defer

Important

  • Never fix without plan approval
  • Fix documented issues only
  • Re-review required

Related Skills

Looking for an alternative to fix or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer