crowi-fix

Fixes bugs with a repro-first workflow, root-cause analysis, and a single-pass adversarial review.

1.1k|165|Updated Aug 18, 2014
One-click install
npx skills add https://github.com/crowi/crowi --skill crowi-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crowi-fix
Source: https://github.com/crowi/crowi/tree/main/.claude/skills/crowi-fix
Command: npx skills add https://github.com/crowi/crowi --skill crowi-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bug fixes often get done ad hoc: no reproduction, guesswork patches, and symptom-hiding workarounds. This Skill standardizes a lightweight bug-fix workflow for the Crowi codebase that requires a failing test first, identifies the root cause before touching code, and enforces quality gates before commit.

Core Features & Use Cases

  • Repro-first discipline: Write a failing test (Jest + supertest + mongodb-memory-server for the API) before any fix; bugs that cannot be reproduced are not fixed by guesswork.
  • Systematic root-cause debugging: Iterate symptom → hypothesis → verification until the root cause is pinpointed at file:line, avoiding symptomatic patches.
  • Gated completion: Run type-check, targeted tests, and lint (plus contract build and OpenAPI checks when contracts change), then a single-pass codex adversarial review whose findings are either fixed or dropped.
  • Use Case: A user reports that a wiki page API returns stale data. The Skill writes a failing API test reproducing the staleness, traces the root cause to a cache invalidation line, applies a minimal diff, passes all gates, runs the codex review, and commits with a fix(<scope>) message plus a changeset.

Quick Start

Ask the assistant to fix a specific bug in the Crowi codebase using the crowi-fix workflow, starting with a failing reproduction test.

Frequently Asked Questions about crowi-fix

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

FAQPage Schema
How do I fix a bug in the Crowi codebase with a failing test first?

Write a failing test that reproduces the bug before changing any code, using Jest with supertest and mongodb-memory-server for the API package. The bug is considered fixed only when that test turns green, which prevents guesswork patches.

When should I use a lightweight bug-fix workflow instead of a full feature workflow?

Use the lightweight fix workflow when behavior is broken, the expected outcome is clear, and no design decisions are needed. If the change adds new behavior, modifies contracts or schemas, or involves trade-offs, escalate to the design or feature workflow instead.

What quality gates run before committing a bug fix?

Run pnpm type-check for the API (and web if touched), the relevant tests including the reproduction test, and pnpm lint with zero errors. If API contracts changed, also build the api-contract package and run the OpenAPI check.

How does the codex single-pass review handle findings?

Each finding is either fixed or dropped: verify it against the code, apply the fix and rerun gates if correct, or discard it with a one-line note if wrong. Deferring findings to a backlog is not allowed, and review tool failures never block the fix.

What happens if a bug cannot be reproduced?

Bugs that cannot be reproduced are not fixed, because speculative patches are prohibited. The workflow stops and asks the user for reproduction conditions instead of guessing at a cause.