skills.rest
dthuy62
dthuy62COMMUNITY
Explore all skills by this author →
GitHub

ck:fix

Diagnose and fix software defects with regression tests and verification.

Updated May 10, 2026
Search Tags:#ci/cd#debugging#root cause#bug fixing#verification#lint#regression tests
One-click install
npx skills add https://github.com/dthuy62/kollet-app --skill ck-fix-dthuy62
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:fix
Source: https://github.com/dthuy62/kollet-app/tree/main/.opencode/skills/fix
Command: npx skills add https://github.com/dthuy62/kollet-app --skill ck-fix-dthuy62

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a disciplined workflow for diagnosing and fixing software problems without guesswork, helping you resolve bugs faster while avoiding symptom-only patches.

Core Features & Use Cases

  • Root-cause analysis: Scans the affected area first, then traces failures back to the originating cause instead of patching the visible error.
  • Multi-path issue handling: Supports bugs, test failures, CI/CD breakages, lint and type errors, log errors, and UI issues with mode selection and complexity routing.
  • Verification and prevention: Requires exact before-and-after verification, regression coverage, and defensive checks so the same issue class does not return.
  • Use Case: A failing test or production bug can be investigated systematically, fixed with minimal changes, and validated with follow-up checks before completion.

Quick Start

Ask the ck:fix skill to investigate the failing issue, identify the root cause, apply the minimal fix, and verify the result with tests and safety checks.

Frequently Asked Questions about ck:fix

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

FAQPage Schema
How do I fix CI/CD build failures and test regressions without guessing?▼

Diagnosing software defects requires structured scouting and root cause tracing to identify the originating failure. This process works across multi-file codebases by mapping dependencies before applying minimal fixes to prevent symptom-only patches.

What is the best way to diagnose root cause bugs in a multi-file codebase?▼

Diagnosing root cause bugs in a multi-file codebase requires scanning the affected area and tracing failures back to their origin. This method ensures you resolve the actual defect rather than patching visible errors like UI issues or log errors.

How do I systematically fix type errors and lint errors in my code?▼

To fix type errors and lint errors systematically, select the appropriate issue mode and route by complexity. Apply the minimal code change, then verify the exact before-and-after state to ensure the fix is complete and safe.

Can I use a single workflow to handle UI issues, test failures, and log errors?▼

Yes, a single multi-path issue handling workflow supports UI issues, test failures, and log errors. It uses mode selection and complexity routing to apply the correct diagnostic and implementation steps for each specific failure type.

How do I prevent the same software defect from happening again after a fix?▼

To prevent the same software defect from returning, require exact before-and-after verification, add regression test coverage, and implement defensive checks. This ensures the specific issue class is permanently resolved after the fix.

Related Skills

Explore More Software Engineering Skills→
hotriluanhotriluan

ck:fix

Automate end-to-end bug fixing with scout, diagnose, and verify steps.

Community
Advanced
jammindevjammindev

bug

Reproduce software bugs, add failing regression tests, and verify fixes.

Official
Advanced
timequitytimequity
6

ci-cd-pipelines

Automate CI/CD pipeline design and deployment workflows for GitHub Actions and GitLab CI.

Official
Advanced
mostafasudomostafasudo
3

gstack-openclaw-investigate

Debug software issues through symptom collection, pattern analysis, and hypothesis testing.

Community
Advanced