npx skills add https://github.com/equinor/fusion-skills --skill fusion-issue-authoring此技能使用内部代理模式来处理特定类型的问题起草逻辑:
agents/bug.agent.md: 专注于 Bug 的问题起草和分类结构agents/feature.agent.md: 专注于功能的范围和验收结构agents/user-story.agent.md: 角色/工作流/场景驱动的故事结构agents/task.agent.md: 清单优先的任务分解和依赖关系规划代理模式根据问题类型分类在内部激活。用户从不直接引用代理文件。共享的关卡(标签、负责人确认、草稿审查、发布确认和变更序列)保留在此技能中。
当您需要将想法、Bug、功能请求或用户需求转化为清晰、可操作的 GitHub 问题时,请使用此技能。将其用作创建和更新问题的顶级路由器。
典型触发条件:
请勿将此技能用于:
This skill uses internal agent modes for type-specific drafting logic:
agents/bug.agent.md: bug-focused issue drafting and triage structureagents/feature.agent.md: feature-focused scope and acceptance structureagents/user-story.agent.md: role/workflow/scenario-driven story structureagents/task.agent.md: checklist-first task decomposition and dependency planningAgent modes are activated internally based on issue type classification. Users never reference agent files directly. Shared gates (labels, assignee confirmation, draft review, publish confirmation, and mutation sequencing) remain in this skill.
Use this skill when you need to turn ideas, bugs, feature requests, or user needs into clear, actionable GitHub issues. Use it as the top-level router for both creating and updating issues.
Typical triggers:
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
发布前收集:
.tmp/ 缓存文件。@me 或确切的登录名时,跳过候选搜索。如果缺少必需的详细信息,请根据 references/questions.md 提出简洁的澄清问题。如果不清楚问题目的地,请在起草变更命令之前明确询问问题应在何处创建/更新。
将请求分类为 Bug、Feature、User Story 或 Task,然后激活匹配的代理模式:
agents/bug.agent.mdagents/feature.agent.mdagents/user-story.agent.mdagents/task.agent.md如果模糊不清,仅询问必要的澄清问题。
CONTRIBUTING.md、contribute/),这些指南可能定义了按类型的默认问题路由。在询问用户之前,应用在那里找到的任何路由规则。.github/ISSUE_TEMPLATE/)在起草/发布之前,使用 mcp_github::search_issues 运行一次集中的重复项搜索并展示匹配项。除非用户实质性更改范围/标题,否则不要运行重复的广泛重复项扫描。
使用 GitHub Flavored Markdown 在 .tmp/{TYPE}-{CONTEXT}.md 中起草。
变更前确认:
@me、特定登录名或不分配)共享关卡缓存策略:
owner/repo 查找标签时,获取一次仓库标签集并为活动会话缓存。当主机暴露会话内存时,优先使用 /memories/session/<owner>-<repo>-labels.json;否则使用 .tmp/issue-authoring-labels-<owner>-<repo>.json。mcp_github::issue_write 调用中仅包含用户确认的标签,并处理单个拒绝路径。@me 或确切的 GitHub 登录名时,跳过 mcp_github::search_users。/memories/session/<owner>-<repo>-assignee-candidates.json 或 /memories/session/<owner>-assignee-candidates.json;否则使用 .tmp/issue-authoring-assignee-candidates-<owner>-<repo>.json。在明确确认后,按此顺序执行 MCP 变更:
mcp_github::issue_write 使用完整的已知负载(title、body,并且仅在支持时包含 labels、assignees、type)创建/更新mcp_github::issue_writemcp_github::sub_issue_writemcp_github::add_issue_comment如果由于缺少 MCP 服务器/认证/配置而导致变更失败:
references/mcp-server.md 中的设置步骤速率限制行为:
API rate limit exceeded、secondary rate limit、GraphQL 配额耗尽)。gh api/GraphQL 重试。retry-after 和 x-ratelimit-reset 头部信息。type 规则:
type。mcp_github::list_issue_types。type。链接前:
使用 references/instructions.md 和 references/mcp-server.md 中的详细行为和负载示例。
使用 references/instructions.md 中的详细创作指导。备用模板位置:
assets/issue-templates/bug.mdassets/issue-templates/feature.mdassets/issue-templates/user-story.mdassets/issue-templates/task*.md.tmp/ 下的草稿问题文件路径Awaiting user content approval绝不:
mcp_github::issue_write 创建/更新始终:
owner/repo#123)fixes owner/repo#123、resolves owner/repo#123 或 closes owner/repo#123)每周安装数
93
仓库
首次出现
2026年2月20日
安全审计
安装于
github-copilot92
codex79
kimi-cli79
gemini-cli79
cursor79
opencode79
Do not use this skill for:
Collect before publishing:
.tmp/ cache file that is never committed.@me or an exact login.If required details are missing, ask concise clarifying questions from references/questions.md. If issue destination is unclear, ask explicitly where the issue should be created/updated before drafting mutation commands.
Classify request as Bug, Feature, User Story, or Task, then activate the matching agent mode:
agents/bug.agent.mdagents/feature.agent.mdagents/user-story.agent.mdagents/task.agent.mdIf ambiguous, ask only essential clarifying questions.
CONTRIBUTING.md, contribute/) that define default issue routing by type. Apply any routing rules found there before asking the user..github/ISSUE_TEMPLATE/)Run one focused duplicate search with mcp_github::search_issues and surface matches before drafting/publishing. Do not run repeated broad duplicate scans unless the user changes scope/title materially.
Draft in .tmp/{TYPE}-{CONTEXT}.md using GitHub Flavored Markdown.
Before mutation, confirm:
@me, specific login, or unassigned)Shared gate cache policy:
owner/repo, fetch the repository label set once and cache it for the active session. Prefer /memories/session/<owner>-<repo>-labels.json when the host exposes session memory; otherwise use .tmp/issue-authoring-labels-<owner>-<repo>.json.mcp_github::issue_write call and handle a single rejection path.mcp_github::search_users when the user already gave @me or an exact GitHub login./memories/session/<owner>-<repo>-assignee-candidates.json or /memories/session/<owner>-assignee-candidates.json; otherwise use .tmp/issue-authoring-assignee-candidates-<owner>-<repo>.json.After explicit confirmation, execute MCP mutations in this order:
mcp_github::issue_write create/update with the full known payload (title, body, and include labels, assignees, type only when supported)mcp_github::issue_write only when required fields were unknown in step 1 and become available latermcp_github::sub_issue_write only when relationship/order changes are requestedmcp_github::add_issue_comment only when blocker/status notes are explicitly requestedIf mutation fails due to missing MCP server/auth/config:
references/mcp-server.mdRate-limit behavior:
API rate limit exceeded, secondary rate limit, GraphQL quota exhaustion).gh api/GraphQL retries when equivalent MCP capability exists.retry-after and x-ratelimit-reset headers before retrying any request.type rule:
type if the repository has issue types configured.mcp_github::list_issue_types only on cache miss or invalid cache.type for the rest of the session.Before linking:
Use detailed behavior and payload examples in references/instructions.md and references/mcp-server.md.
Use detailed authoring guidance in references/instructions.md. Fallback template locations:
assets/issue-templates/bug.mdassets/issue-templates/feature.mdassets/issue-templates/user-story.mdassets/issue-templates/task*.md.tmp/Awaiting user content approval before any publish/update commandNever:
mcp_github::issue_write create/update without explicit user confirmationAlways:
owner/repo#123)fixes owner/repo#123, resolves owner/repo#123, or closes owner/repo#123)Weekly Installs
93
Repository
First Seen
Feb 20, 2026
Security Audits
Installed on
github-copilot92
codex79
kimi-cli79
gemini-cli79
cursor79
opencode79
agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试
163,300 周安装