菜单
Commit all current changes, push to a feature branch, and create a PR. Use when the user asks to commit, push, save progress, or ship changes.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/LalitMaganti/syntaqlite --skill cp命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Quickly commit and push current changes to a feature branch and create a PR, skipping pre-push checks. WARNING: if CI starts failing, use /cp instead.
Debug a SQL formatter bug. Use when the user reports incorrect formatting, such as wrong whitespace, misplaced comments, or blank lines.
Format SQL files using the syntaqlite formatter. Use when the user wants to format, reformat, or pretty-print SQL code.
基于 SOC 职业分类
正在显示 SKILL.md
| name | cp |
| description | Commit all current changes, push to a feature branch, and create a PR. Use when the user asks to commit, push, save progress, or ship changes. |
| user_invocable | true |
Commit all current changes, push to a feature branch, and open a pull request. All pre-push checks must pass before pushing.
Run pre-push checks with auto-fix (quiet mode suppresses output on success):
tools/pre-push --fix -q
If this fails, fix the issues and re-run until it passes. Do NOT skip this step; it is the project's only gate against broken code.
Check for changes:
git status
git diff --stat
git log --oneline -5
Stage all changes (including any fixes from step 1):
git add -A
Write a commit message following the project convention:
synq: (lowercase)Commit using a HEREDOC:
git commit -m "$(cat <<'EOF'
synq: <summary>
<optional body>
EOF
)"
Create a feature branch if on main:
If currently on main, create and switch to a descriptive branch:
git checkout -b <branch-name>
Branch naming: use lowercase kebab-case describing the change (e.g.,
add-cte-column-validation, fix-fmt-trailing-comma). No prefixes needed.
Push the branch:
git push -u origin HEAD
Create a PR using gh pr create. For single-commit PRs the
body should be the commit body verbatim; the lead-in + bullets
structure from step 4 is exactly the structure a PR wants. Don't
rewrite it into a single paragraph, don't add section headings,
don't restate the title. The shortcut:
git log -1 --format=%b HEAD | gh pr create --title "<title>" --body-file -
For multi-commit PRs, write the body in the same shape (short lead-in + bullets covering the important changes across commits). One-liners are fine only when the title and diff genuinely speak for themselves.
synq: Report the PR URL to the user.