跳到正文
cccskills
免费在 GitHub 公开

pr

Commit the current changes on a new branch, push, and open a GitHub PR following this repo's conventions.

中文简介正在准备中。当前显示原文说明。

howard36/probase星标 20(GitHub 20 + cccskills 0)
集成工具GitHub

实测评分 未实测

查看安装方法

包含的文件（1）

  • SKILL.md1.2 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Optional PR title or branch hint: $ARGUMENTS

  1. Run /verify first. Do not open a PR with failing lint, Prettier, or build.
  2. If on main, create a branch: descriptive kebab-case, no prefix (e.g. one-time-use-invites). Derive the name from the change or from the arguments.
  3. Review git status and git diff before staging. Never stage .env* files (other than .env.example).
  4. Commit with a Conventional Commits subject: <type>: <short imperative description>, lowercase description (types: feat, fix, refactor, chore, docs, style, ci). End the message with the Co-Authored-By and Claude-Session trailers the session provides.
  5. Push with git push -u origin <branch>.
  6. Open the PR with gh pr create. Title matches the commit subject. Body: what changed and why, in a few sentences. If the PR includes a Prisma migration, say so in the body and note it will apply to production on merge.
  7. Reply with the PR URL.

PRs are rebased into main, so keep commits clean and self-contained rather than relying on squash.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护，适用 Google 的隐私权政策和服务条款。

同一仓库的技能

prisma-migrate

免费

Create a Prisma migration for a schema change against the local database. Use after editing prisma/schema.prisma.

中文简介正在准备中。当前显示原文说明。

howard36/probase202026年9月26日 更新

verify

免费

Verify a change is done by running lint, the Prettier check, the test suites, and a production build. Use after finishing any code change and before opening a PR.

中文简介正在准备中。当前显示原文说明。

howard36/probase202026年9月26日 更新

查看 howard36 的全部技能

报告此技能的问题