harehare-mq-cli-instructions.ocm.json json {
"ocm": "1",
"id": "harehare-mq-cli-instructions",
"kind": "skill",
"name": "cli",
"description": "CLI Tool Coding Rules",
"publisher": "harehare",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"skill-md",
"github-instructions"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"CLI Tool Coding Rules"
],
"primary": false,
"metadata": {
"source": {
"provider": "github-instructions",
"repository": "https://github.com/harehare/mq",
"path": ".github/instructions/cli.instructions.md",
"ref": "4c6912365837fcd6c2a9f61b9383179d2daaa13a",
"url": "https://github.com/harehare/mq/blob/4c6912365837fcd6c2a9f61b9383179d2daaa13a/.github/instructions/cli.instructions.md",
"key": "harehare/mq/.github/instructions/cli.instructions.md"
},
"applies_to": "crates/mq-run/**/*.rs"
},
"instructions": "# CLI Tool Coding Rules\n\n- All command-line interface logic must reside in `mq-run`.\n- Use `clap` or similar crate for argument parsing.\n- Provide clear, user-friendly error messages using `miette`.\n- Document all commands, flags, and options in code and in the CLI help output.\n- Write integration tests for CLI behavior and edge cases.\n- Ensure the CLI is robust against malformed input and unexpected usage.\n- Output should be clear and suitable for piping/automation.",
"cost": {
"context_tokens": 117
}
}