菜单
Vendor-neutral wrapper for appending a Validation Journey section to an existing ticket/issue. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-add-journey, lisa:github-add-journey, or lisa:linear-add-journey.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CodySwannGT/grist --skill tracker-add-journey命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective.
Build or Refactor large Rails controller files into clean, maintainable code. Use when a controller action exceeds ~10 lines, a controller has custom non-RESTful actions, or when the user asks to refactor, slim down, clean up, or organize a Rails controller. Applies patterns: service objects, query objects, form objects, controller concerns, presenters/decorators, and RESTful resource extraction.
Best practices for Ruby on Rails models, splitting code into well-organized, maintainable code. Use when a model exceeds ~100 lines, has mixed responsibilities, or when the user asks to refactor, extract, clean up, or organize a Rails model. Applies patterns: concerns, service objects, query objects, form objects, and value objects.
| name | tracker-add-journey |
| description | Vendor-neutral wrapper for appending a Validation Journey section to an existing ticket/issue. Reads `tracker` from .lisa.config.json (default: jira) and dispatches to lisa:jira-add-journey, lisa:github-add-journey, or lisa:linear-add-journey. |
| allowed-tools | ["Skill","Bash","Read"] |
Thin dispatcher. Resolves the configured destination tracker and delegates to the matching vendor skill.
See the config-resolution rule for configuration and dispatch table.
lisa:tracker-write).jira → invoke lisa:jira-add-journey with $ARGUMENTS verbatim. Arg: a JIRA ticket key.github → invoke lisa:github-add-journey with $ARGUMENTS verbatim. Arg: org/repo#<number> or a GitHub issue URL.linear → invoke lisa:linear-add-journey with $ARGUMENTS verbatim. Arg: a Linear Issue identifier (e.g., ENG-123)."Unknown tracker '<value>' in .lisa.config.json. Expected 'jira', 'github', or 'linear'."[EVIDENCE: name] markers). The only difference is how the section is appended — JIRA via editJiraIssue (Jira wiki markup), GitHub via gh issue edit --body-file (markdown), Linear via save_issue (markdown).