skills.rest
hotriluan
hotriluanCOMMUNITY
Explore all skills by this author →
GitHub

ck:fix

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

1|Updated Mar 5, 2026
Search Tags:#automation#workflow#diagnosis#verify#root-cause#fixing#scout
One-click install
npx skills add https://github.com/hotriluan/alkana_web --skill ck-fix-hotriluan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ck:fix
Source: https://github.com/hotriluan/alkana_web/tree/main/.opencode/skills/fix
Command: npx skills add https://github.com/hotriluan/alkana_web --skill ck-fix-hotriluan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill provides a structured, automated workflow for fixing bugs by guiding through Scout, Diagnose, and Verify stages, ensuring root-cause analysis and prevention of regressions.

Core Features & Use Cases

  • Automated mode selection and coordinated multi-agent debugging
  • Mandatory steps: Scout, Diagnose, Complexity Assessment, Fix, Verify, and Finalize
  • Parallel exploration and task orchestration for larger issues
  • Prevention measures including regression tests and defense-in-depth validation
  • Real-world use: triaging flaky tests, fixed bugs across modules, and UI regressions

Quick Start

Initiate ck:scout, ck:debug, and ck:sequential-thinking to start the end-to-end fix workflow on the failing project.

Frequently Asked Questions about ck:fix

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

FAQPage Schema
How do I automate end-to-end bug fixing workflows with strict root-cause analysis?▼

End-to-end bug fixing workflows are automated by guiding mandatory scout, diagnose, fix, and verify steps to ensure root-cause analysis. This process applies to bugs, lint issues, CI/CD problems, and UI regressions across modules, preventing future regressions.

What is the best way to diagnose flaky tests and CI/CD pipeline failures?▼

Diagnosing flaky tests and CI/CD failures is best handled through a structured scout, complexity assessment, and verify workflow. This approach enforces root-cause diagnosis and coordinates parallel subagents to triage and fix the failing modules systematically.

How do I fix UI regressions and architecture issues across multiple modules?▼

Fixing UI regressions and architecture issues across modules requires parallel exploration and task orchestration. The automated workflow guides multi-agent debugging through mandatory scout, diagnose, and verify stages to resolve the root cause and prevent regressions.

Does this automated debugging workflow support parallel subagents for large issues?▼

Automated debugging workflows do support parallel subagents for larger issues. The process coordinates multi-agent debugging through complexity assessment and parallel exploration to triage bugs, test failures, and CI/CD problems across modules.

How do I prevent regressions when applying bug fixes to failing projects?▼

Preventing regressions when applying bug fixes requires mandatory verification and finalization steps. The workflow adds regression tests and defense-in-depth validation after the root-cause fix to ensure the failing project remains stable.

Related Skills

Explore More Software Engineering Skills→
benzwickbenzwick

download-ci-artifacts

Download GitHub Actions CI artifacts using gh CLI commands.

Community
Intermediate
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
raykrayk
3

coordinate-subagents

Coordinate subagents with parallel calls, token budgets, and voting.

Community
Advanced
HmbownHmbown
105

investigation

Diagnose root causes by connecting logs, traces, docs, and code clues.

Community
Advanced