菜单
Proactively update SKILL.md files when they become outdated, incorrect, or need improvements. Use when you notice a skill doesn't match current workflow, when user corrects your skill usage, or when discovering better practices that should be documented.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run affected tests, typecheck, and lint (with autofix) to catch CI failures locally before pushing. Use when CI is failing or before pushing to avoid CI failures. Offers to fix typecheck/test failures and to amend+push when clean.
Create a GitHub PR for the current branch with auto-generated description. Use when the user asks to create a pull request, open a PR, or put up changes for review.
Create a Linear ticket for the current branch on the One Big Team, auto-assigning the appropriate Linear project and team/product labels based on which part of the codebase changed. Use when the user asks to create a Linear ticket, file a Linear issue, or track work in Linear for changes on the current branch.
Render, read, and add component examples in the examples renderer. Files take two forms — colocated `*.examples.tsx` (e.g. `Checkbox.examples.tsx` next to `Checkbox.tsx`) or grouped `examples/*.tsx` (e.g. `Checkbox/examples/Default.tsx`). Covers exact iframe URLs per example, story-id derivation, multi-worktree-aware server discovery, file conventions, and the onboarding gate. Onboarded products (the authoritative validation list — only invoke this skill when the work touches one of these): `apps/staff/`. Verify at runtime with `nx show projects --with-target examples`. Use to render, screenshot, inspect, or extend an example in an onboarded product. For anything outside the onboarded list, this skill does not apply.
Create a Storybook story for a component. Use when the user asks to add a story, write a story, or create a Storybook story for a component.
Go through a PR's review comments one by one, propose solutions, and commit fixes. Use when the user wants to address PR feedback, review comments, or resolve PR review requests.
| name | maintain-skill-files |
| description | Proactively update SKILL.md files when they become outdated, incorrect, or need improvements. Use when you notice a skill doesn't match current workflow, when user corrects your skill usage, or when discovering better practices that should be documented. |
This skill defines when and how to proactively update SKILL files to improve future interactions.
Core principle: If you notice that a skill needs updating, offer to update it immediately. Don't wait for the user to ask.
Watch for these signals that a skill needs updating:
name: and description: fields (see "Skill Format Requirements" below)Skills are specific, repeatable workflows or procedures. Create or update skills for:
Location:
.claude/skills/<skill_name>/SKILL.md (relative to repo root)
When you notice a signal from the "When to Update" section, immediately consider:
Tell the user what you want to update and why. For example:
"I notice you had to correct me about using the issue template. I should update the create_recidiviz_data_github_tasks skill to make that more explicit. Would you like me to do that?"
OR if it's very obvious:
"I'm going to update the skill to include this step since it's part of the workflow."
After updating:
For official best practices on writing SKILL files, see the Skills documentation.
CRITICAL: All skills MUST have YAML frontmatter with name: and description: fields. This is how Claude autonomously discovers when to use skills.
Required format (from official docs):
---
name: your-skill-name
description: Brief description of what this Skill does and when to use it. Use when [specific trigger phrases].
---
Requirements:
name: Lowercase letters, numbers, and hyphens only (max 64 characters)description: Max 1024 characters. Must include:
Example:
---
name: create-github-tasks
description: File GitHub issues and tasks. Use when the user asks to file, create, or track issues, tasks, tickets, or TODOs.
---
When updating skills: If a skill doesn't have this frontmatter, or if the user complains the skill wasn't triggered, add or improve the YAML frontmatter with clear trigger terms in the description.
Signal: User says "I'm annoyed that you still needed to be prompted to follow the issue template structure"
Action:
Signal: While following the "create GitHub task" skill, you discover that if the task is for a different repo, the TODO format is different
Action:
Signal: User says "Also make sure to add the 'Team: Data Platform' label"
Action:
Signal: User walks you through a complex multi-step process that you'll likely do again
Action:
.claude/skills/<workflow_name>/SKILL.md with clear steps