omk-test-debug-loop
Debug failing lint, typecheck, test, and build commands with minimal fixes and repeated verification.
git clone --depth 1 https://github.com/dmae97/open-multi-agent-kit /tmp/omk-test-debug-loop && cp -r /tmp/omk-test-debug-loop/templates/skills/kimi/omk-test-debug-loop ~/.claude/skills/omk-test-debug-loopSKILL.md
## Test Debug Loop Use this when a command fails. ## Steps 1. Capture exact command and output. 2. Classify failure: - syntax - type - dependency - runtime - test assertion - environment - flaky 3. Identify the smallest related file set. 4. Fix the root cause, not the symptom. 5. Re-run the failing command. 6. Run adjacent checks if needed. 7. Stop after repeated failure and report blocker. ## Rules - Do not make broad refactors while debugging. - Do not weaken tests unless the test is demonstrably wrong. - Do not delete failing tests to pass. - Do not ignore type errors. ## Report ```txt Failing command: Failure class: Root cause: Fix: Re-run result: Remaining risk: ```
Persistent memory, recall, session replay, and memory-governance workflow adapted from rohitg00/agentmemory for OMK. Use when setting up agent memory, deciding what to remember, importing/replaying sessions, reducing repeated context, or auditing memory safety.
Minimal, goal-driven, surgical coding workflow adapted from forrestchang/andrej-karpathy-skills for OMK. Use for coding, refactoring, debugging, and review tasks where assumptions, overengineering, or broad edits could cause regressions.
Legal workflow drafting, triage, review, research planning, legal operations, law-student or clinic support, and legal AI governance adapted from Anthropic claude-for-legal. Use for commercial, privacy, product, corporate, employment, regulatory, AI governance, IP, litigation, legal-clinic, and law-student tasks. Draft-only; attorney review and current source verification required.
Real-engineering alignment, shared-language, TDD, diagnosis, and architecture-review workflow adapted from mattpocock/skills for OMK. Use before non-trivial implementation, ambiguous product work, debugging loops, test-first changes, or codebase architecture cleanup.
Managed-agent teamwork, issue assignment, progress tracking, reusable-skill compounding, and handoff workflow adapted from multica-ai/multica for OMK. Use when coordinating multiple agents, converting work into agent-ready tasks, tracking blockers, or turning repeated solutions into skills.
Review AdaptOrch, OMK, and similar DAG multi-agent orchestration frameworks. Use when assessing DAG node responsibility, dependency edges, worker write authority, fallback/retry/timeout/evidence gates, review/merge boundaries, or reproducible decision traces.
Optional read-only OMK web/social/video research workflow inspired by Panniantong/Agent-Reach. Use for web search, current social evidence, YouTube/Bilibili/Reddit/Twitter/X/RSS/GitHub public research, and Agent Reach availability checks without auto-installing or collecting credentials.
Backend API review for NestJS, Express, FastAPI, database access, validation, auth, error handling, and API contracts.