mkfix
SolidDiagnoses and fixes bugs, type errors, lint failures, CI/CD issues, and runtime errors via root-cause-first investigation. Use for defect remediation. NOT for investigation without a fix (see mk:investigate); NOT for build-only compilation errors (see mk:build-fix).
Install
Quality Score: 86/100
Skill Content
Details
- Author
- ngocsangyem
- Repository
- ngocsangyem/MeowKit
- Created
- 4 months ago
- Last Updated
- today
- Language
- TypeScript
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
mkinvestigate
Systematic debugging with root cause investigation. Produces a diagnostic report; mk:fix owns remediation and mk:build-fix owns compile/build failures. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working. NOT for applying fixes without investigation (see mk:fix); NOT for step-by-step evidence-based reasoning (see mk:sequential-thinking).
fix
Use when repairing a concrete bug, regression, failing test, stack trace, or broken behavior. Diagnose only as far as needed to make a minimal verified repair, then write one `fixed.md` record. Use scout or independent review when the cause, blast radius, or risk is uncertain; do not impose incident ceremony on a local fix.
fix
Use when the user says "fix", "make it pass", or "apply the findings", or hands a verifier failure or bug description.