菜单
Open pull requests for the current git repo: verify you are not on main/prod, compare your branch to main, commit any pending work, and create a PR (prefer gh). Use when asked to open or create a PR, draft a PR description, or automate the PR workflow for a local git branch.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Clean up AI-generated writing by removing slop (generic tone, filler, inflated claims, vague attributions, list spam) while keeping meaning the same. Use when asked to "humanize" text, remove AI-sounding writing, or align prose with local/author voice.
Write and edit in a clear, direct style that avoids AI-sounding artifacts. Use whenever drafting or rewriting prose (docs, READMEs, PR descriptions, issues, blog posts, emails, UI copy) and when aligning to the author's preferred voice.
Clean up AI-generated code changes by reviewing diffs against main and removing stylistic or structural artifacts (over-commenting, unnecessary defensive checks, try/catch noise, any-casts, inconsistent style). Use when asked to “remove AI code slop,” “humanize” changes, or align a branch’s edits with existing codebase conventions.
Refactor AGENTS.md instructions to follow progressive disclosure and AGENTS.md best practices. Use when asked to audit, reorganize, or split AGENTS.md into a minimal root file plus linked docs; includes contradiction checks, essential extraction, grouping, and deletion flags.
Plan commits from the current working tree. Use when asked how to split changes into commits, what to stage together, how to handle untracked files, or to propose commit messages and an execution plan (stage/commit) based on `git status`/diffs.
General coding principles for writing clean, maintainable code. Use for development work, code reviews, refactoring, dependency changes, and design discussions about code structure, performance, and reliability.
| name | open-pr |
| description | Open pull requests for the current git repo: verify you are not on main/prod, compare your branch to main, commit any pending work, and create a PR (prefer gh). Use when asked to open or create a PR, draft a PR description, or automate the PR workflow for a local git branch. |
Create a pull request from the current branch to main, ensuring the branch is valid, changes are committed, and the PR description follows the required format.
GIT_EDITOR=true to every git command.main or prod:
GIT_EDITOR=true git rev-parse --abbrev-ref HEADmain or prod, stop and explain why you cannot proceed.main:
GIT_EDITOR=true git fetch origin main (if origin exists)GIT_EDITOR=true git log --oneline main..HEADGIT_EDITOR=true git diff --stat main...HEADmain does not exist locally or remotely, stop and ask how to proceed.GIT_EDITOR=true git status --porcelainGIT_EDITOR=true git add -AGIT_EDITOR=true git commit -m "<message>"Use this exact format:
<feature_area>: <Title> (80 characters or less)
<TLDR> (no more than 2 sentences)
<Description>
- 1~3 bullet points explaining what's changing
command -v gh.GIT_EDITOR=true git push -u origin <branch>gh is available, create the PR:
gh pr create --base main --head <branch> --title "<title>" --body "<body>"gh is not available, explain the manual steps to open a PR on the hosting service.gh pr view --json url -q .url