command-routing

# commands ## When to use Triggered when user invokes a slash command. The `slash-command-routing-policy` rule (always loaded) handles core behavior — this skill adds context inference and GitHub API patterns. ## Procedure: Execute a command 1. **Match command** — Find the command file in `.augment/commands/` or `agents/overrides/commands/`. 2. **Infer inputs** — Before asking the user, try to infer values (see table below). 3. **Execute steps** — Follow the command steps in exact order. 4. **Verify output** — Confirm expected result was produced (commit, PR, file change, etc.). Before asking the user for input, try to infer it: | Input needed | How to infer | |---|---| | Jira ticket | Extract from branch name (`fix/DEV-1234-...` → `DEV-1234`) | | Default branch | `git symbolic-ref refs/remotes/origin/HEAD` or assume `main` | | Project type | Check for `artisan` (Laravel) or `composer.json` (Composer) | | Module name | Extract from current working directory or file path | | Current branch | `git branch --show-current` | Only ask the user if inference fails and the command cannot proceed without the value. ## Command locations | Location | Scope | |---|---| | `.augment/commands/` | Shared commands (work across projects) | | `agents/overrides/commands/` | Project-specific overrides (used instead of original) | ## Commands that dispatch to the work engine Most commands are pure markdown procedures — the agent reads the steps and executes them. Two commands delegate to...