用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/trycompai/crm --skill create-draft-pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository. Use whenever a user asks to add anti-slop lint rules, copy the anti-slop plugin, configure opinionated Oxlint rules, or migrate an existing local anti-slop setup.
Use when an app uses @pierre/diffs to render or edit code files, diffs, patches, merge conflicts, or CodeView review surfaces, including React, vanilla JavaScript, SSR, workers, annotations, selection, and custom Shiki languages or themes.
Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.
基于 SOC 职业分类
正在显示 SKILL.md
| name | create-draft-pr |
| description | Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant. |
| user-invocable | true |
Commit all changes, push to remote, and create a draft pull request with a focused generated description.
git status to see changesgit diff to understand what changedgit log to see commit message stylemain, create a new branch in the format <initials>/<feature> or the project's branch naming convention, then switch to it-u flagpr-description skill's description format.ux-flow-plan style.gh pr create --draftmain), switch back to main after the PR is createdUse the pr-description skill's format as the base:
## Summary
<One sentence describing the overall change>
- Additional note if needed
- Another note if needed
## Problem
Describe the issue being addressed. What was broken, missing, or suboptimal? Be specific about the root cause.
## Solution
Explain the approach taken to fix the problem. Include code snippets only when they clarify the core approach.
When relevant, add this section between Problem and Solution:
## UX Flow
```text
Current flow
└─ ...
Desired flow
└─ ...
```
Only include UX Flow when it helps explain the product behavior, user journey, or architecture boundary. Keep it short and use the ux-flow-plan tree style.
pr-description as the source of truth for PR body structure.UX Flow from ux-flow-plan only when relevant; omit it for mechanical, dependency, or tiny internal changes.