fusion-issue-solving by equinor/fusion-skills
npx skills add https://github.com/equinor/fusion-skills --skill fusion-issue-solving当用户希望端到端地解决或继续处理 GitHub issue 时使用此技能,包括简短的当前仓库提示如 solve #123、直接的 GitHub issue URL,或类似 lets work on https://github.com/owner/repo/issues/123 的请求。
典型触发词:
对于 solve、fix、implement、continue、 或 这类动词,将 GitHub issue URL 视为与 引用可互换。当没有其他竞争意图时,直接的 GitHub issue URL 也可以作为此工作流程的主要请求负载。
Use this skill when the user wants to solve or continue a GitHub issue end-to-end, including short current-repo prompts like solve #123, direct GitHub issue URLs, or requests like lets work on https://github.com/owner/repo/issues/123.
Typical triggers:
Treat GitHub issue URLs as interchangeable with #123 references for verbs like solve, fix, implement, , , or . A direct GitHub issue URL can also serve as the main request payload for this workflow when no competing intent is stated.
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
finishwork on#123在以下情况不要使用此技能:
执行前收集:
owner/repo#number,可选输入:
gh api 或 GraphQL 调用。fusion-issue-authoring 或其下属技能时,协调器的会话缓存规则适用:每个仓库获取一次标签和负责人候选,每个组织获取一次 issue 类型。retry-after 和 x-ratelimit-reset 头部;在指示的等待时间之前不要重试。.tmp/ 目录下,使用特定于 issue/上下文的名称(例如,.tmp/pr-body-issue-123-scope-summary.md)草拟 PR 正文,而不是使用共享的 .tmp/pr-body.md。.github/pull_request_template.md 起草,并随着实现的进展保持更新。main,或当前分支切出的分支)。.tmp/ 目录下的 PR 正文草稿文件,根据已确认的基础分支、草稿/就绪状态、负责人选择和相关的 issue 链接,创建或更新 PR。返回一份简洁的交付报告,包含:
.tmp/ 草稿文件路径)。每周安装数
73
仓库
首次出现
2026年3月2日
安全审计
安装于
github-copilot73
opencode66
gemini-cli66
codex66
kimi-cli66
cursor66
continuefinishwork onDo not use this skill when:
Collect before execution:
owner/repo#number,Optional inputs:
Ask whether to use a dedicated git worktree
Confirm issue context and success criteria
Confirm assignee intent for issue closure work
Apply low-token GitHub strategy
gh api or GraphQL calls when equivalent tools exist.fusion-issue-authoring or its subordinate skills, the orchestrator's session-cache rules apply: labels and assignee candidates are fetched once per repository, issue types once per organization.retry-after and x-ratelimit-reset headers; do not retry before the indicated wait.Build and track a concrete plan
Research before edits
Implement in small scoped changes
Validate incrementally
Prepare PR-ready output
.tmp/ file with an issue/context-specific name (for example, .tmp/pr-body-issue-123-scope-summary.md), not a shared .tmp/pr-body.md..github/pull_request_template.md and keep it updated as implementation evolves.main, or the branch the current branch was cut from).Optional GitHub mutation steps
.tmp/ PR body draft file, using the confirmed base branch, draft/ready state, assignee choice, and related issue links.Return a concise delivery report with:
.tmp/ draft file path when created).Weekly Installs
73
Repository
First Seen
Mar 2, 2026
Security Audits
Installed on
github-copilot73
opencode66
gemini-cli66
codex66
kimi-cli66
cursor66
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
163,300 周安装
通过Rube MCP实现Make自动化:集成Composio工具包管理场景与操作
72 周安装
Microsoft Teams自动化指南:通过Rube MCP实现频道消息、聊天与会议管理
72 周安装
Electrobun 最佳实践:TypeScript + Bun 跨平台桌面应用开发指南
72 周安装
ATXP Memory:AI代理记忆管理工具 - 云端备份与本地向量搜索
72 周安装
Brave Search Spellcheck API:智能拼写检查与查询纠正,提升搜索准确性
72 周安装
Amazon竞品分析器 - 自动化抓取ASIN数据,深度分析竞争对手定价、规格与评论
72 周安装