菜单
Detect (and optionally repair) drift between a project's configured Lisa status/label mappings and the live tracker/source workflow names. Read-only by default; repairs the config to canonical live names with repair=true. Audits the current repo or sweeps many via projects=/workspaces=.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CodySwannGT/grist --skill lisa-validate-tracker-mapping命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 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 | lisa-validate-tracker-mapping |
| description | Detect (and optionally repair) drift between a project's configured Lisa status/label mappings and the live tracker/source workflow names. Read-only by default; repairs the config to canonical live names with repair=true. Audits the current repo or sweeps many via projects=/workspaces=. |
/lisa:validate-tracker-mapping$lisa-validate-tracker-mapping or a plain-English request that matches this skill.[projects=<glob> | workspaces=<file> [filter=<substr>]] [lane=build|prd|both] [repair=true]Use the /lisa:validate-tracker-mapping skill to check whether the status/label names in .lisa.config.json still match the live tracker and PRD source — catching renames, deletions, and case drift (e.g. config On Stg vs live ON STG). Read-only by default; pass repair=true to rewrite the config to the canonical live names. Use the user's surrounding request as this command's arguments.
Common usage:
/lisa:validate-tracker-mapping — audit the current repo's mapping (read-only)./lisa:validate-tracker-mapping repair=true — audit and repair config drift in the current repo./lisa:validate-tracker-mapping projects=~/workspace/geminisportsai/projects/* — sweep every Lisa project under a directory./lisa:validate-tracker-mapping workspaces=~/workspace/lisa/.lisa.workspaces.json filter=geminisportsai — sweep the projects in a workspaces file whose paths match a substring.Use this when you suspect a JIRA/GitHub/Linear/Notion status, label, or option was renamed or deleted out from under Lisa — the failure mode that leaves builds unable to find their completion transition and items silently stuck. Run it read-only (or on a schedule) to detect drift; run it with repair=true to fix the config. Repair only ever edits the config to match the live names — it never renames anything in the tracker.