菜单
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.
用 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.
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.
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.
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 | push |
| description | 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. |
Push the current branch without rewriting remote history.
git status --short --branch.git log @{u}..HEAD --oneline.git push -u origin <branch> and show the local commits that would be introduced remotely.git push, or the approved git push -u origin <branch> form. Never force-push.