ask-anhoder

Routes user tasks to the appropriate om-* workflow skill and executes it.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill ask-anhoder-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ask-anhoder
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/ask-anhoder
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill ask-anhoder-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working in a repository with dozens of specialized agent skills often do not know which skill fits their task, and manually chaining multi-step workflows (issue to PR to merge) is error-prone. This Skill acts as a routing map that selects the correct om-* skill and invokes it automatically. ## Core Features & Use Cases - Automatic skill routing: Maps natural-language task descriptions to one of 36 om-* skills covering issue fixing, PR lifecycle, review, QA, UX, and release chores. - Ambiguity handling: When multiple skills could apply, it presents candidates with one-line scenarios and waits for user selection instead of guessing. - End-to-end execution: Loads the target skill's SKILL.md, parses arguments, executes its workflow verbatim, and preserves machine-readable chain lines (PR:, Issue:, Spec:, Next:) for downstream automation. - Use Case: A user says "fix issue #142 and get it merged" — the router selects om-auto-fix-issue, executes its full chain (verify, root-cause, fix, open PR, review), and reports the resulting PR. ## Quick Start Describe your task in plain language, such as asking to route and run the right skill for fixing a specific issue or advancing a pull request to merge.

Frequently Asked Questions about ask-anhoder

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

FAQPage Schema
How do I choose the right agent skill for a development task?

Describe your task in plain language and the router matches it to one of the om-* skills, such as om-auto-fix-issue for bugs or om-auto-create-pr for feature briefs. When the routing is unambiguous it invokes the target skill automatically rather than only suggesting it.

How to automate the workflow from issue to merged pull request?

Route the issue to om-auto-fix-issue, which chains verification, root-cause analysis, fixing, PR creation, and automated review. Marker lines like PR: and Next: let subsequent skills continue the chain without manual handoff.

What happens when multiple skills could handle my request?

The router stops and lists each candidate skill with a one-line scenario and a recommendation, then waits for you to pick one. It never auto-invokes a skill when routing is ambiguous, and it asks clarifying questions when key parameters like issue or PR numbers are missing.

Can I use skill routing for read-only questions without changing anything?

Yes, read-only consultations route to non-mutating skills such as om-merge-buddy for merge readiness, om-root-cause for issue analysis, and om-pipeline-retro for pipeline cost review. These produce reports without claiming issues or modifying the repository.

What are the limitations of automatic skill routing?

The router does not invent steps or bypass the target skill's gates, and it stops when the target skill reports blocked status or requires human decisions. Interactive skills like om-brainstorm keep their own confirmation gates, which the router does not override.