skills.rest
dmae97
dmae97COMMUNITY
Explore all skills by this author →
GitHub

omk-troubleshooting

Diagnose build and test failures by capturing stack traces and verifying minimal fixes.

130|14|Updated Apr 30, 2026
Search Tags:#debugging#troubleshooting#agent workflow#test failures#build failures#dependency conflicts
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-troubleshooting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omk-troubleshooting
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/agents/omk-troubleshooting
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill omk-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically diagnose and resolve build failures, test failures, environment issues, dependency conflicts, and agent workflow blockers without guessing.

Core Features & Use Cases

  • Error-first diagnosis: Capture the exact error message and stack trace to anchor the investigation.
  • Repro and scope reduction: Identify the smallest reproducible scope to isolate the root cause.
  • Minimal verified remediation: Apply the smallest fix possible and confirm it by re-running the failing command, while documenting persistent root causes in risk memory.

Quick Start

Ask the AI to troubleshoot your latest failing command by requesting the exact error message, identifying the smallest reproducible scope, and proposing a minimal fix you can verify immediately.

Frequently Asked Questions about omk-troubleshooting

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

FAQPage Schema
How do I troubleshoot a build failure when the root cause is unclear?▼

To troubleshoot a build failure, capture the exact stack trace, narrow the issue to the smallest reproducible scope, validate dependencies, and apply a minimal verified fix by re-running the failing command.

What is the best way to fix test failures in a local development environment?▼

Fixing test failures requires structured diagnosis: capture the exact error message, isolate the reproducible scope, apply the smallest possible remediation, and verify the fix by re-running the original failing test command.

How do I resolve dependency conflicts during a CI run?▼

Resolving dependency conflicts involves validating your environment and packages, identifying the exact error, narrowing to the failing scope, applying minimal fixes, and verifying with the original failing CI command.

Can I use structured troubleshooting to fix multi-agent workflow blockers?▼

Yes, you can fix multi-agent workflow blockers by capturing the interruption's exact error, isolating the reproducible scope, applying a minimal fix, and verifying the resolution by re-running the interrupted workflow.

Why should I record persistent root causes when diagnosing environment issues?▼

Recording persistent root causes for environment issues in risk memory prevents recurring failures, ensuring that the minimal verified fixes applied to your dependencies and setup are documented for future diagnosis.

Does troubleshooting agent workflow interruptions require specific environment data?▼

Troubleshooting agent workflow interruptions requires capturing exact stack traces and validating the current environment and dependencies to accurately narrow the failure to a reproducible scope before applying fixes.

Related Skills

Explore More Software Engineering Skills→
FrekiManagarmFrekiManagarm

error-tracking-node

Configure PostHog exception tracking for Node.js applications with source maps.

Community
Intermediate
dixusdixus
10

debug

Diagnose and fix failing tests, type errors, or runtime errors.

Community
Advanced
SatoryKonoSatoryKono
1

py-debug-bot

Execute the py-debug-bot profile to validate BioETL workflow constraints.

Community
Intermediate
ClaudioCeppi83ClaudioCeppi83

error-detective

Analyze error patterns and stack traces to identify root causes.

Community
Advanced