/commit-optimization
Use when configuring settings.json to reduce fuse-commit-pro's context token usage.
$ npx -y skills add fusengine/agents --skill commit-optimization --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/commit-optimization
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when configuring settings.json to reduce fuse-commit-pro's context token usage.
SKILL.md
commit-optimization.SKILL.mdname: commit-optimization description: Use when configuring settings.json to reduce fuse-commit-pro's context token usage.
<objective> Documents the `includeGitInstructions: false` settings.json option (and its `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1` env var override, which takes precedence) that removes Claude Code's built-in commit/PR workflow instructions from the system prompt — saving 2-5% context tokens — since fuse-commit-pro supplies its own comprehensive git workflow that supersedes the defaults. </objective>
Commit Optimization
Optimization: Disable Built-in Git Instructions
For best results with fuse-commit-pro, add this to your `~/.claude/settings.json`:
{
"includeGitInstructions": false
}This removes Claude Code's built-in commit/PR workflow instructions from the system prompt, saving 2-5% context tokens. fuse-commit-pro provides its own comprehensive git workflow that supersedes the defaults.
Note: `CLAUDE_CODE_DISABLE_GIT_INSTRUCTIONS=1` env var takes precedence over this setting.
A plugin ecosystem that turns Claude Code into a supervised, multi-agent development environment.
Repo: fusengine/agents
Other skills on fusengine-agents.
- /agent-creator
Use when creating expert agents. Generates agent.md with frontmatter, hooks, required sections, and skill references.
Open skill - /apex-methodology
Use when starting ANY development task -- feature, bug fix, refactor, hotfix (triggers: implement, create, build, fix, add feature, refactor, develop).
Open skill - /brainstorming
Use when creating a feature/component or adding functionality. Fires BEFORE APEX Analyze to refine requirements via structured questioning.
Open skill - /challenge
Use before a root-cause, done/verified claim, irreversible action, or 2nd-time fix reaches the owner (APEX or plain conversation); also fires at every eLicit/Verify gate. Not for code correctness (use sniper).
Open skill - /code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
Open skill - /elicitation
Use when an expert agent self-reviews and self-corrects code after the Execute phase, before sniper validation (BMAD-METHOD elicitation techniques).
Open skill

