使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill fix-decision-router开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
fix-decision-router Skill
Purpose: Present post-capture options and execute user's choice after fix-reporter creates documentation.
Decision Menu
Present after successful documentation:
Solution documented
File created:
- .agents/lessons/[category]/[filename].md
What's next?
1. Continue workflow (recommended)
2. Add to Critical Patterns
3. Link related issues
4. Add to existing skill
5. Create new skill
6. View documentation
7. Enable discovery
8. OtherOption Handlers
Option 1: Continue workflow
- Return to calling skill/workflow
- Documentation complete, no further action
Option 2: Add to Critical Patterns
When user selects: Pattern is non-obvious but must be followed every time.
1. Extract pattern from the documentation
2. Format as WRONG vs CORRECT (use template below)
3. Append to .agents/lessons/patterns/critical-patterns.md
4. Add cross-reference back to source doc
5. Confirm: "Added to Critical Patterns"Template:
markdown
## N. [Pattern Name] (Required)
### WRONG ([Will cause X error])[code showing wrong approach]
### CORRECT[code showing correct approach]
**Why:** [Technical explanation]
**Context:** [When this applies]
**Source:** `.agents/lessons/[category]/[filename].md`Option 3: Link related issues
1. Prompt: "Which doc to link? (filename or describe)"
2. Search .agents/lessons/ for matching doc
3. Add cross-reference to both docs under "## Related Issues"
4. Confirm: "Cross-reference added to both files"Option 4: Add to existing skill
1. Prompt: "Which skill?"
2. Find skill in plugins/*/skills/
3. Determine target: resources.md, patterns.md, or examples.md
4. Add link and brief description
5. Confirm: "Added to [skill-name] in [file]"Option 5: Create new skill
1. Prompt: "Skill name?"
2. Create directory: plugins/majestic-engineer/skills/[name]/
3. Create SKILL.md with basic structure
4. Add solution as first example in references/
5. Confirm: "Created [skill-name] skill"Option 6: View documentation
1. Read and display the created file
2. Present decision menu againOption 7: Enable discovery
Make lesson discoverable by lessons-discoverer agent:
1. Prompt workflow phases: [planning, debugging, review, implementation]
2. Prompt tech stacks: [rails, python, react, node, generic]
3. Prompt lesson type: [antipattern, gotcha, pattern, setup, workflow]
4. Update YAML frontmatter with:
- workflow_phase: [selected phases]
- tech_stack: [selected stacks]
- lesson_type: [selected type]
- impact: Derive from severity
- keywords: Extract from tags + symptoms
5. Confirm: "Lesson discoverable during [phases] workflows"Impact mapping:
- critical → blocks_work
- high → majortimesink
- medium/low → minor_inconvenience
Option 8: Other
Prompt for custom action and execute.
Integration
Invoked by: fix-reporter (after Step 7) Invokes: None (terminal options)
Input Schema
yaml
doc_path: string # Path to created documentation
category: string # Problem category from fix-reporter
