skills.rest
hidonguyen
hidonguyenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ck:fix

Diagnose and fix code issues with verification and regression prevention.

Updated Apr 2, 2026
Search Tags:#debugging#verification#root-cause#bugfix#ci#task-orchestration
One-click install
npx skills add https://github.com/hidonguyen/trade-ops --skill ck-fix-hidonguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:fix
Source: https://github.com/hidonguyen/trade-ops/tree/main/.opencode/skills/fix
Command: npx skills add https://github.com/hidonguyen/trade-ops --skill ck-fix-hidonguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a disciplined, evidence-first workflow to fix bugs, test failures, CI/CD errors, type/lint problems, and UI defects while avoiding symptom-only patches and recurring regressions. It enforces mandatory scouting and structured diagnosis before any fix, and requires verification plus prevention steps so changes are safe, minimal, and auditable.

Core Features & Use Cases

  • Structured Workflow: Stepwise scout → diagnose → assess complexity → implement fix → verify & prevent → finalize, with explicit outputs for each step.
  • Modes & Routing: Supports autonomous, human-in-the-loop, quick (trivial fixes), deep (research + planning), and parallel multi-agent workflows.
  • Tooling & Orchestration: Integrates Task-based orchestration, parallel Explore/Bash agents, and mandatory activation of ck:scout, ck:debug, and ck:sequential-thinking; includes review and docs update gates.
  • Prevention Gate: Always captures pre-fix state, requires regression tests or runtime assertions, and applies defense-in-depth where applicable.
  • Use Case: Triage a failing test or CI job, trace the root cause across modules, implement a minimal fix with a regression test, then run parallel verification (typecheck, lint, build, tests) before finalizing.

Quick Start

Use the ck:fix skill to run a fast scout→diagnose→fix→verify cycle for a simple type or lint error in the repository.

Frequently Asked Questions about ck:fix

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

FAQPage Schema
How do I fix recurring CI failures without just patching the symptoms?▼

Fix recurring CI failures by executing a structured scout, diagnosis, and verified fix workflow that traces the root cause across modules and mandates regression tests to prevent symptom-only patches.

What is the best way to debug complex multi-file architecture bugs?▼

Debug complex multi-file architecture bugs using a deep workflow that captures pre-fix state, diagnoses evidence-first, implements minimal fixes, and applies defense-in-depth with mandatory regression tests.

How do I orchestrate parallel agents to triage multiple test failures?▼

Triage multiple test failures by using Task-based orchestration with parallel Explore and Bash agents to execute simultaneous diagnosis, fix implementation, and verification across typecheck, lint, build, and tests.

Can I use a quick fix workflow for simple type and lint errors?▼

Yes, a quick workflow mode supports trivial single-file type and lint errors by running a fast scout, diagnose, fix, and verify cycle without requiring deep research or multi-agent orchestration.

Does this bugfix workflow require human-in-the-loop approval?▼

The bugfix workflow supports autonomous, human-in-the-loop, deep, and parallel modes, allowing you to configure mandatory approval gates for diagnosis, fix implementation, review, and documentation updates.

Why do I need to capture pre-fix state before debugging code issues?▼

Capturing pre-fix state before debugging code issues ensures changes are safe, minimal, and auditable, providing a baseline to validate mandatory verification and prevention steps like regression tests and defense-in-depth.

Related Skills

Explore More Software Engineering Skills→
DaddyElonMusk69DaddyElonMusk69

systematic-debugging

Identify software bug root causes using a four-phase debugging process.

Community
Intermediate
GantisStormGantisStorm
6

code-quality

Run type checking and linting on staged code changes via start.sh.

Community
Basic
The-RabakThe-Rabak

slrj

Orchestrate autonomous engineering workflows with swarm-based task delegation across multiple agents.

Community
Advanced
Chai-UnChai-Un

fix

Fix lint errors and formatting issues using yarn, prettier, and linc.

Community
Intermediate