fusion-rules
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.
How do I install this agent skill?
npx skills add https://github.com/equinor/fusion-skills --skill fusion-rulesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill acts as a gateway for authoring AI coding assistant rules across GitHub Copilot, Cursor, and Claude Code. It orchestrates sub-agents to scan project documentation and generate configuration files. The main security consideration is that the skill processes untrusted repository content (like READMEs and ADRs) which could contain malicious instructions aimed at biasing the generated rules. However, the skill explicitly mandates user review of drafts and diffs before any filesystem changes occur, which serves as a significant safeguard.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
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
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/equinor/fusion-skills/fusion-rules">View fusion-rules on skillZs</a>