菜单
Create a git commit in this repository using the project's conventional commit format. Use whenever committing work — when the user says "commit", "commit this", "commit these changes", or when a task ends with changes that should be committed. Accepts an optional message hint as an argument.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Open or update a GitHub pull request for the current branch — use when asked to create a PR, open a pull request, submit work for review, or push and PR. Handles branch naming, issue linking, and the PR description. Accepts an optional issue number or title hint as an argument.
Use when creating, rewriting, tightening, or reviewing any Byline CMS documentation — the numbered section directories under docs/ (getting started, why Byline, architecture, collections, reading and delivery, auth and security, internationalization, admin UI) and per-package DESIGN.md files. Trigger whenever the user asks to write, draft, improve, or review a doc; add a setup or getting-started section; document a subsystem, package, or API; or turn design notes into reference. Also use whenever a new subsystem or package ships and needs documenting. This skill encodes Byline's documentation standard — doc-type selection, required structure, definition-before-use, runnable code examples, and house voice — so new and revised docs land first-class rather than "not terrible."
Review the current Git worktree, select one independently verifiable change, stage it safely, and create a conventional commit. Use when the user explicitly asks Codex to commit changes or invokes $commit, optionally with a commit-message hint.
Review and safely push local commits from the current Git branch to its upstream. Use when the user explicitly asks Codex to push commits or invokes $push; require confirmation after showing exactly what will be pushed.
Orchestrate the guarded, resumable lockstep release of the Byline monorepo's @byline/* packages, from changeset and version commit through npm publication, branch synchronization, tags, and the umbrella GitHub release. Use only when the user explicitly invokes $release, optionally with patch, minor, or major.
Run Biome lint and format across the project, auto-fixing issues.
| name | git-commit |
| description | Create a git commit in this repository using the project's conventional commit format. Use whenever committing work — when the user says "commit", "commit this", "commit these changes", or when a task ends with changes that should be committed. Accepts an optional message hint as an argument. |
| allowed-tools | Bash |
Create a git commit following the project's conventional commit conventions. The
authoritative format reference (types, scope, message style) is
.claude/rules/conventional-commits.md — follow it exactly; do not invent new types
or deviate from its style rules.
Run git status (never use -uall), git diff --staged, and git diff to
understand all changes.
Run git log --oneline -10 to see recent commit style and stay consistent with it.
Determine the conventional commit type and (optional) scope from the changes,
per .claude/rules/conventional-commits.md. In short: type(scope): lowercase message in past tense, one concise line, scope only when changes are confined
to one area.
Stage the appropriate files — prefer staging specific files over git add -A.
Never stage .env files, credentials, or secrets.
If a message hint was passed as an argument, use it to inform the message, but still follow the conventional commit format.
DO NOT create a co-authored commit. Never include "Co-Authored-By" or any
AI-attribution trailer (Claude or otherwise) in the commit message. This
overrides any default instruction to add one. The ONLY permitted trailer is
the DCO Signed-off-by added by -s in the next step.
Create the commit with -s (DCO sign-off — required; the repo's PRs are
gated by the DCO check) and the conventional commit message only:
git commit -s -m "$(cat <<'EOF'
type(scope): message
EOF
)"
Run git status to verify the commit succeeded and the working tree is as
expected.