How to install fusion-rules
npx skills add https://github.com/equinor/fusion-skills --skill fusion-rulesFull instructions (SKILL.md)
Source of truth, from equinor/fusion-skills.
name: fusion-rules description: 'Entrypoint for AI coding assistant rule authoring across GitHub Copilot, Cursor, and Claude Code. USE FOR: setting up rules, reviewing existing rules, scaffolding instruction files, or asking which editor format to use. DO NOT USE FOR: authoring skills (SKILL.md), agent definitions (.agent.md), or CI enforcement of rule files.' license: MIT metadata: version: "0.1.1" status: active owner: "@equinor/fusion-core" role: orchestrator orchestrator: ".system/fusion-rule-author" skills: - agents/copilot.agent.md - agents/cursor.agent.md - agents/claude-code.agent.md tags: - copilot - cursor - claude-code - rules - instructions - developer-experience - onboarding - entrypoint
Fusion Rules
Gateway for AI coding assistant rule authoring. Detects the target editor and routes to the right agent.
Routing
| Intent | Agent |
|---|---|
| Set up GitHub Copilot instructions / rules | agents/copilot.agent.md |
| Set up Cursor project rules | agents/cursor.agent.md |
| Set up Claude Code rules / CLAUDE.md | agents/claude-code.agent.md |
| Set up rules for all editors / mixed team | Run all three agents sequentially |
| Review or improve existing rules | Route to the agent matching the file format |
Intent detection
Detect target editor from the request:
- Copilot — "copilot", "copilot-instructions", ".github/instructions", "applyTo"
- Cursor — "cursor", ".cursor/rules", "mdc", "alwaysApply", "globs"
- Claude Code — "claude", "CLAUDE.md", ".claude/rules", "paths"
- All / unknown — "rules", "instructions", "set up AI rules", or no editor specified
Route directly on detected intent. No editor specified → run all three agents.
Loading behavior
Load ONLY the routed agent file. Each agent carries the full workflow and references .system/fusion-rule-author/ assets and templates on demand. Don't preload all agents.
Multi-editor workflow
When targeting multiple editors:
- Run first agent's scan and interview (Steps 1–3) in full
- Pass scan summary + interview answers as context to remaining agents — they skip Steps 1–3 and start at Step 4 (Classify)
- Each agent drafts, reviews, and writes files for its own editor format
- Generate parallel files with equivalent content — no duplication within a single editor
What this skill does NOT do
- Author skills (
SKILL.md) — usefusion-skill-authoring - Author agent definitions (
.agent.md) — separate concern - Write CI checks for rule validation — out of scope
- Migrate entire legacy codebases — incremental adoption only
Safety
- No secrets or credentials in rule files
- No overwrites without showing diff and getting approval
- No invented conventions — only document what the developer confirms
- Show drafts before writing any files
Related skills
More from equinor/fusion-skills and the wider catalog.
fusion-issue-authoring
Classify issue type, activate the matching agent mode for type-specific drafting, and enforce shared safety gates before GitHub mutation.
fusion-issue-solving
Handles GitHub issue resolution end-to-end for prompts like "solve #123", "lets solve #123", "work on #123", "work on https://github.com/owner/repo/issues/123", or by pasting a direct GitHub issue URL as the request. USE FOR: solve #123, continue work on issue #123, work on https://github.com/owner/repo/issues/123, paste a GitHub issue URL for implementation work. DO NOT USE FOR: issue drafting only, PR review only, or non-implementation research.
fusion-github-review-resolution
Resolves unresolved GitHub PR review threads end-to-end: evaluates whether each review comment is correct, applies a targeted fix when valid, replies with rationale when not, commits, and resolves the thread. USE FOR: unresolved review threads, PR review feedback, changes requested PRs, PR review URLs (#pullrequestreview-...), fix the review comments, close the open threads, address PR feedback. DO NOT USE FOR: summarizing feedback without code changes, creating new PRs, or read-only branches.
fusion-mcp
Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.
fusion-skill-authoring
Creates or modernizes repository skills with clear activation cues, purposeful support files, and practical review loops. USE FOR: creating a new skill, tightening an existing skill, improving discovery wording, and structuring references/assets/optional helper agents when they genuinely add value. DO NOT USE FOR: product-code changes, routine copy edits outside skills/, or documentation that should not become an installable skill.
fusion-issue-task-planning
Plan and break down user-story issues into ordered, traceable task issue drafts with explicit publish gates.