본문으로 건너뛰기
cccskills
무료GitHub에 공개

ck:fix

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

ck:fix — Structured Bug-Fix Pipeline

Modes — mutually exclusive, pick one (default = Standard: auto-approve on code-reviewer's own APPROVED verdict):

  • --fast — trivial issues (lint, type errors, build errors); skip scout, review, docs
  • --hard — mandatory review, no auto-approve

Report-scoped input (either replaces Step 0's free-text description):

  • --from-quality <report-path> — the target is exactly the blocking findings in a ck:quality report (plans/{slug}/quality/{phase}-quality-report.json).
  • --from-test <report-path> — the target is exactly the failures in a ck:test failure report.

With either flag, fix strictly what the report lists — no expanding scope to adjacent code the report doesn't cite, even if it looks related.


Step 0 — Prerequisites + Scope

--from-quality/--from-test: read the report; its findings/failures are the scope. Skip straight to Step 2 (report evidence replaces Scout).

Otherwise, if no error message, stack trace, or concrete description provided: → "Paste the error message or stack trace." Wait before continuing.

# Scope:
#   Description: {what the user said, or "from {report-path}"}
#   Quick?      → {yes/no — reason}
#   Mode:       {Standard | Quick | Hard}

If --fast or clearly a build/compiler/lint error: skip Step 1 → go directly to Step 2.


Step 1 — Scout

Skip if --from-quality/--from-test (the report already is the evidence).

Spawn scout with the bug description:

  • Greps for error patterns in logs and stack traces
  • Reads affected source files and maps dependencies
  • Checks recent git changes for related commits
// Evidence:
//   Error pattern: NullReferenceException at auth.ts:45
//   Affected files: auth.ts, session.ts
//   Recent change: commit a3f2b1 modified auth.ts (2h ago)

Step 2 — Diagnose

Spawn debugger with the scout evidence report, or with the report's findings/failures directly for --from-quality/--from-test:

  • Forms 2–3 hypotheses from the evidence (or takes the report's required_action/expected vs actual directly — it's already a confirmed root cause, not a hypothesis)
  • Confirms or rejects each against the codebase
  • Applies the minimal fix at the confirmed root cause, scoped to exactly what the report/evidence names
// Hypothesis A: null check missing in auth.ts:45 → CONFIRMED ✓
// Hypothesis B: race condition in session init   → REJECTED ✗
//
// Root cause: missing null guard on req.user before .validate()
// Fix applied: auth.ts:45
// Severity: HIGH | Scope: 1 file

Step 2.5 — Quality Re-verification (when applicable)

If the fix touched any file already covered by an issued quality receipt (plans/{slug}/quality/{phase}-receipt.json), that receipt is now stale — its fingerprint no longer matches the file's bytes. Run ck:quality --verify plans/{slug}/quality/{phase}-quality-report.json before Step 3. CHANGES_REQUIRED sends the fix back to Step 2; do not proceed to Review or Finalize on a stale or rejected receipt.

Skip this step only when the fix touched no file with an existing receipt.


Step 3 — Review

--fast: skip → Step 4.

Spawn code-reviewer: correctness, security, regressions. code-reviewer does not re-score maintainability that ck:quality already approved in Step 2.5 — it checks the bug fix itself, not architecture.

Standard: auto-approve on code-reviewer's APPROVED verdict. Up to 3 fix/re-review cycles (different approach each), then escalate. --hard: no auto-approve — human must explicitly approve before Step 4.


Step 4 — Finalize (MANDATORY)

project-manager (skip --fast): sync plan progress if bug was tracked. docs-manager (skip --fast): update docs if fix changes a public contract. git-manager (always): conventional commit + ask to push.

// git-manager → fix(auth): add null guard on req.user before validate
//            → Push to remote? [y/N]

Agents

AgentStepModes
scout1Standard, --hard (skip if --fast or --from-quality/--from-test)
debugger2All
ck:quality --verify2.5All (only when a touched file has an existing receipt)
code-reviewer3Standard, --hard (skip for --fast)
project-manager4Standard, --hard (skip for --fast)
docs-manager4Standard, --hard (skip for --fast)
git-manager4Always (mandatory)

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

caveman

무료

Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

ck-cook

무료

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

ck-fix

무료

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

ck-plan

무료

Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

DangQuangSE의 스킬 모두 보기

이 스킬의 문제 신고