Menu
DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update bug issues using a bug-focused structure.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
Explain what Fusion MCP is and guide users through setting it up when they need Fusion-aware MCP capabilities in Copilot workflows.
Explain what Fusion PM MCP is and guide setup of the hosted HTTP+OAuth server for its GitHub project-management retrieval tools. USE FOR: setting up or troubleshooting Fusion PM MCP, understanding its issue/PR/milestone tools, filing a setup bug. DO NOT USE FOR: implementing changes to the fusion-pm-mcp service itself, GitHub issue authoring/triage workflows, or general Fusion Framework/docs/EDS retrieval โ use `fusion-mcp` for that.
Provision and migrate Fusion databases using the fusion-infra-cli (finf). USE FOR: provision a database for a service, run SQL migrations, provision PR-specific ephemeral databases, check database state. DO NOT USE FOR: application code changes, service deployments, role management, or infrastructure other than databases.
Deploy and manage Fusion Roles V2 configuration using the fusion-roles-cli (froles). USE FOR: deploy role config from a JSON file, create roles/bindings/assignments, export current role state, inspect role assignments. DO NOT USE FOR: database provisioning, application code changes, Azure AD group management outside role bindings, or Roles V1 management.
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.
| name | fusion-issue-author-bug |
| description | DEPRECATED: Use fusion-issue-authoring instead. Previously: Draft and update bug issues using a bug-focused structure. |
| license | MIT |
| metadata | {"version":"0.1.3","status":"deprecated","deprecated_at":"2026-03-18","successor":"fusion-issue-authoring","owner":"@equinor/fusion-core","orchestrator":"fusion-issue-authoring","role":"subordinate","tags":["github","issue-authoring","bug","deprecated"],"mcp":{"required":["github"]}} |
DEPRECATED: This skill has been consolidated into
fusion-issue-authoring. Install onlyfusion-issue-authoringfor full bug/feature/user-story/task authoring capability. See equinor/fusion-core-tasks#802 for details.
Requires fusion-issue-authoring as the top-level orchestrator for classification, shared gates, and publish flow.
Use this skill when the request is about broken behavior, regressions, crashes, or unexpected results.
Do not use this skill for feature requests, user stories, or generic enablement tasks.
Bug..tmp/BUG-<context>.md.Template fallback:
skills/fusion-issue-author-bug/assets/issue-templates/bug.md.tmp/Do not perform mutation directly; mutation stays in fusion-issue-authoring.