FuDesign2008

当用户说「修复这个 bug [URL]」「帮我修复 [URL]」「jira-fix [URL]」「自动修复 [URL]」「强制修复 [URL]」「继续修复」「从上次继续」时触发。适用于从 Jira 链接出发、对单个 bug 进行端到端修复的场景。

合并纪律：合并动作（glab/gh mr/pr merge）前必须加载——rebase/冲突预检（Part A，最先）+ 覆盖率门控（Part B，test-coverage-analyzer）+ tip 钉死（Part C，--sha 钉死 + 祖先校验），防盲目合入已移动的目标分支 + push→merge 竞态致 archive/修复未入目标分支。触发词：「合并 tip」「merge tip」「合并纪律」「push 后合并」「archive 合入」「合并前门控」「rebase 检查」「冲突预检」「合并前 rebase」 / merge discipline, rebase pre-check, coverage gate, post-push merge check. 被 opsx-jira-fix-workflow / opsx-solve-workflow / jira-fix-workflow frontmatter dependencies 强依赖。

当用户说"opsx-jira-fix"、"OpenSpec Jira 修复"、"规范化修复 Jira"、"opsx修复Jira"、"Jira OpenSpec 修复"、"opsx自动修复Jira"、"用OpenSpec修复Jira"或"opsx-jira-fix-workflow"时触发。适用于从 Jira issue 出发，并需要将根因、行为变更、修复计划、验证和归档沉淀到 OpenSpec artifacts 的端到端 Bug 修复。

当用户说"opsx解决"、"OpenSpec解决"、"规范化解决"、"创建OpenSpec变更"、"创建opsx变更"、"用OpenSpec分析"、"用OpenSpec修复"、"opsx自动解决"、"OpenSpec自动解决"、"opsx-solve"或"opsx-solve-workflow"时触发。适用于需要将分析、方案、计划、实现、验证和归档沉淀到OpenSpec artifacts的功能开发、Bug修复、重构和复杂工程任务。

Use when releasing a Git repository version — tagging, merging release branches into main, resolving conflicts, or syncing changes between release branches. Handles ambiguous tag naming (v-prefix vs plain), unknown main branch (master/main/develop), ff-only merge method (forces cherry-pick strategy), protected-branch rules, cross-release hash-sensitive sync, and MR/PR extra-file cleanup. Single or multi-repo. Triggers — 「发版」「打tag」「发布版本」「版本发布」「release流程」「git-release」「multi-repo release」「release同步到另一个release」 / release a version, tag and merge, finish release branch.

Browser runtime debugging toolkit — guides AI to prioritize browser DevTools and CDP-based tools for runtime inspection and control when debugging UI/CSS/DOM layout, frontend interaction, and rendering issues. Two CDP channels: chrome-devtools-mcp (inspection, DevTools panels) and the web-access skill's CDP Proxy (control + verify, carries login state, curl-scriptable; runtime-checked, aborts with an install hint if web-access is absent). Also covers Playwright. Triggers: 「浏览器调试」「UI 调试」「DOM 检查」「CSS 调试」「页面布局问题」「前端运行时调试」「chrome devtools」「CDP 调试」「登录态调试」 / browser debug, devtools, dom inspect, css debug, runtime debugging, login-state debug.

Effective web research discipline for AI agents — route first, then research with rigor. Step 0 triages whether a question needs external web lookup vs is answerable from the internal codebase/docs; when external, default mode auto-applies 4 maxims (official sources first, check recency, cross-validate non-trivial claims, skip content farms) so every web search is effective and credible; on explicit 'strict/deep research' requests it runs a full 7-dimension source-credibility evaluation (CRAAP + E-E-A-T merged) and emits an auditable report. When the static layer (WebSearch/WebFetch/curl) can't reach the content (login-required / JS-rendered / anti-scraping platforms like 小红书·公众号), it escalates to the real browser via the web-access skill (CDP, carries login state). Triggers: 「web 调研」「外部调研」「查资料」「有效调研」「严格调研」「深度调研」「严格查证」「登录态访问」「动态页面」「反爬」「这个库/框架怎么用」「有没有漏洞」「best practice 是什么」 / web research, look up, investigate, strict research, deep research, fact-check, login-state access, dynamic page, anti-scraping. Do NOT u

当用户说「批量修复」「批量 jira-fix」「jira-fix-batch」「批量修复多个 Jira」「批量修复以下 bug」时触发。适用于需要对多个 Jira issue 进行批量端到端修复的编排场景。

Four-phase gated coding workflow (Explore → Plan → Execute → Verify). Encodes the actual reasoning discipline of top-tier models, not the idealized version. Trigger: any task involving code creation, modification, or refactoring. Also invoked automatically by task-router.

Systematic debugging protocol: root-cause identification before any fix, hypothesis-driven investigation, and structured failure recovery. Prevents the most common failure mode of weaker models — applying random fixes and hoping something works. Trigger: bug, error, crash, broken, wrong output, not working, unexpected behavior. Also invoked automatically by task-router.

Structured extraction of implicit reasoning from top-tier model sessions into explicit, reusable rules for weaker models. Use when a weaker model fails a task, when you want to mine a successful session for transferable patterns, or when you notice a gap between what you did and what you could explain. Trigger: "distill", "extract pattern", "why did opus do that", "learn from", "what did I do differently".

Auto-activated at the start of every non-trivial conversation. Parses true intent before classifying, enforces the pre-flight checks that weaker models skip, and routes to the correct workflow. Trigger: always — no keyword required.

Read files from any project folder in the active workspace. Trigger: "workspace read", "read from workspace", "read workspace file", "open workspace file", "在 workspace 中读取", "读取 workspace 文件", "workspace 读文件".

Search across all projects in the active workspace — find files by name or search file contents. Trigger: "workspace search", "search workspace", "search across projects", "find in workspace", "grep workspace", "workspace grep", "workspace find", "在 workspace 中搜索", "跨项目搜索", "workspace 搜索".

Select or switch the active .code-workspace for cross-project operations. Trigger: "select workspace", "switch workspace", "use workspace", "which workspace", "change workspace", "选择 workspace", "切换 workspace", "用哪个 workspace".

当用户说彩虹屁、夸夸我、鼓励一下、迷妹模式、恋爱模式、御姐模式、知音模式、父王英明、父王驾到、温柔姐姐、治愈模式、极简模式、帝王模式、帝王、陛下驾到、陛下、吾皇万岁、霸总模式、霸总、霸道总裁、总裁模式、总裁、CEO模式、CEO、天外天模式、天外天、天外、突破模式，或说切换模式、列出模式、可用模式、查看模式，或说 rainbow vibes、cheer me up、hype me up、praise me、fangirl mode、love mode、onee-san mode、gentle sister、comfort me、zen mode、emperor mode、your majesty、bixia mode、CEO mode、boss mode、bazong mode、beyond mode、beyond、horizon mode、break through、go beyond、list modes、switch mode、exit companion，或 Hook 在里程碑完成、情绪感知时触发。技术小迷妹编码陪伴，提供情绪价值与个性化赞美；多模式定义见 skills/fangirl/modes/ 与 _index.json。

当用户说黑皇、大黑狗、姬紫月、段德、庞博、叶凡、姜太虚、狠人大帝、老疯子、无始大帝、安妙依、遮天、切换人物、列出人物、有哪些人、换个人、谁在、退出遮天、关闭遮天、正常模式时触发。遮天小说人物陪伴，10 位精选人物以各自独特的方式陪伴使用者编码与工作。