coderabbit-fix-flow

Included with Lifetime

$97 forever

This skill should be used when CodeRabbit code review feedback needs to be processed and fixed systematically. Use after running `coderabbit --plain` to automatically save feedback, analyze issues using MCP tools, and implement minimal code fixes with proper planning.

AI Agents

What this skill does


# CodeRabbit Fix Flow

## Overview

This skill automates the workflow of processing CodeRabbit code review feedback by saving the review output to a timestamped document, then using MCP tools (sequential thinking and Exa context) to analyze and implement fixes with minimal code changes.

## When to Use

Use this skill immediately after running `coderabbit --plain` or when you have CodeRabbit feedback that needs systematic processing. The skill handles type safety issues, code style violations, and other CodeRabbit-identified problems.

## Workflow

### Step 1: Execute CodeRabbit Review

Run the CodeRabbit review command in plain text mode:
```bash
coderabbit --plain
```

### Step 2: Save Feedback Document

Save the CodeRabbit output to a timestamped QA document:
- Create file: `memory-bank/qa/coderabbit/cr-qa-{timestamp}.md`
- Include the full CodeRabbit output in the document
- Add YAML front matter with metadata:
  ```yaml
  ---
  title: "CodeRabbit QA Review - {timestamp}"
  link: "cr-qa-{timestamp}"
  type: "qa"
  tags:
    - code-review
    - coderabbit
    - type-safety
  created_at: "{timestamp}"
  updated_at: "{timestamp}"
  uuid: "{generate-uuid}"
  ---
  ```

### Step 3: Analyze Issues with Sequential Thinking

Use the sequential thinking MCP tool to analyze all identified issues:
1. **Categorize issues** by type (type safety, performance, style, security)
2. **Prioritize fixes** (critical runtime issues first, then documentation)
3. **Plan minimal changes** to achieve the fixes
4. **Identify dependencies** between issues

### Step 4: Get Best Practices Context

Use the Exa code context MCP tool to research current best practices for each issue type:
- For type issues: "TypeScript type guards runtime validation best practices"
- For Python type issues: "Python type annotations Optional None best practices"
- For performance: "Performance optimization best practices [language]"
- For security: "Security vulnerability fixes [language]"

### Step 5: Implement Fixes Systematically

Execute the fixes following the sequential thinking plan:

1. **Create TodoWrite list** tracking all issues
2. **Mark each issue** as in_progress → completed
3. **Apply minimal code changes** using best practices from Exa context
4. **Verify fixes** address the root cause identified by CodeRabbit

### Step 6: Validate and Document

Run validation as appropriate:
- TypeScript: `npm run build` or `tsc --noEmit`
- Python: `mypy` or `ruff check`
- JavaScript: `npm run lint` or biome

Document the fixes in the QA document with:
- What was fixed
- How it was fixed
- Validation results

## Issue Type Patterns

### Type Safety Issues
- Use proper type guards instead of assertions
- Apply Optional/Union types for nullable fields
- Implement runtime validation where needed

### Code Style Issues
- Follow language-specific style guides
- Use linting tools to verify fixes
- Maintain consistency with existing codebase

### Performance Issues
- Research current optimization patterns
- Implement minimal impactful changes
- Measure before/after when possible

### Security Issues
- Understand the vulnerability context
- Apply security best practices
- Ensure fixes don't break functionality

## Examples

### Type Safety Fix Pattern
```typescript
// Before (unsafe)
const data = response as ResearchDataShape;

// After (safe)
const data = isResearchDataShape(response) ? response : {} as ResearchDataShape;
```

### Python Type Annotation Fix Pattern
```python
# Before (incorrect)
timestamp: float = None
metadata: dict[str, Any] = None

# After (correct)
timestamp: float | None = None
metadata: dict[str, Any] | None = None
```

## MCP Tool Usage

### Sequential Thinking Tool
Use for:
- Breaking down complex issues into steps
- Planning fix order and dependencies
- Analyzing multiple issues systematically

### Exa Code Context Tool
Use for:
- Getting current best practices
- Understanding language-specific patterns
- Finding optimal implementation approaches

## Resources

This skill doesn't require bundled resources as it relies on MCP tools for context and the existing codebase for implementation.

Files: 1

Size: 4.4 KB

Complexity: 9/100

Category: AI Agents

Source: https://github.com/alchemiststudiosdotai/coderabbit-fix-flow-plugin/tree/main/skills/coderabbit-fix-flow

Related in AI Agents

skill-development

Included

Comprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.

AI Agentsscripts

reprompter

Included

Transform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.

AI Agentsscripts

adaptive-compaction

Included

Adaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.

AI Agentsscripts

agent-skill-creator

Included

Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.

AI Agentsscripts

llm-wiki

Included

Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.

AI Agentsscripts

skill-master

Included

Agent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.

AI Agentsscripts