plugins/orchestration/skills/orchestration/SKILL.md
Coordinates other skills and agents. ALWAYS use this skill on startup.
npx skillsauth add motlin/claude-code-plugins orchestrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Invoke these skills liberally - most tasks use multiple skills:
| Skill | When to use |
| ----------------------------------- | ------------------------------------- |
| @code:code-quality | Before editing code |
| @code:cli | When running shell commands |
| @build:precommit | Before running builds or tests |
| @git:git-workflow | For all git operations |
| @orchestration:conversation-style | For response guidelines |
| @orchestration:llm-context | When working with .llm/ directories |
ALWAYS delegate to the @git:commit-handler agent for all commit operations. Never run git commit directly.
ALWAYS delegate to the @git:conflict-resolver agent to resolve any git merge or rebase conflicts.
ALWAYS delegate to the @git:rebaser agent to rebase the current branch on upstream.
NEVER write files to /tmp or other system temporary directories - reading from /tmp triggers permission prompts. Write scratch files and temporary outputs to .llm/ instead.
Always run /orchestration:finish before returning control to the user. It handles the case where there's nothing to do.
tools
This skill should be used after completing any task, before returning control to the user. Always run this skill — it handles the case where there's nothing to do.
development
Commit message format and git workflow rules. ALWAYS use this skill for every git commit — no exceptions — and whenever rewording an existing commit message.
tools
CLI guidelines. Use whenever using the Bash tool, which is almost always. Also use when you see "command not found: __zoxide_z" errors.
tools
Maven CLI invocation patterns. Use whenever running `mvn` commands in Java/Maven projects. Covers when `-am` is required, why `-o` (offline) mode hides bugs in multi-worktree setups, and how to verify compile/test cleanly without trusting stale `~/.m2` artifacts.