菜单
Create a conventional commit and push to the current branch. Ensures commit messages follow the Conventional Commits spec for automatic versioning with release-please.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/avihaymenahem/velo --skill commit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Add help documentation for a new or changed feature. Updates the Help page content, project docs (docs/, CLAUDE.md), and keeps counts accurate.
基于 SOC 职业分类
正在显示 SKILL.md
| name | commit |
| description | Create a conventional commit and push to the current branch. Ensures commit messages follow the Conventional Commits spec for automatic versioning with release-please. |
| argument-hint | ["optional commit description"] |
Create a git commit following the Conventional Commits specification. This is required for release-please to auto-determine version bumps.
Check the current state — run git status (no -uall flag) and git diff --staged to understand what's being committed. If nothing is staged, stage the relevant files (prefer specific files over git add .).
Determine the commit type from the changes:
| Type | When to use | Version bump |
|---|---|---|
feat | New feature or capability | minor (0.x.0) |
fix | Bug fix | patch (0.0.x) |
docs | Documentation only | no release |
style | Formatting, whitespace, semicolons (no logic change) | no release |
refactor | Code restructuring (no feature/fix) | no release |
perf | Performance improvement | patch (0.0.x) |
test | Adding or fixing tests | no release |
build | Build system, dependencies, CI | no release |
chore | Maintenance, tooling, configs | no release |
ci | CI/CD pipeline changes | no release |
revert | Reverting a previous commit | depends on reverted type |
Format the commit message strictly as:
type(scope): short description
Optional longer body explaining the "why" (not the "what").
BREAKING CHANGE: description (if applicable)
Rules:
composer, sync, settings, db, ui, ai, calendar, auth, search, shortcuts, tray, notifications, labels, filters, queue, imap, attachments)Examples:
feat(composer): add scheduled send with date picker
fix(sync): handle expired Gmail history token gracefully
refactor(db): consolidate migration helpers
docs: update keyboard shortcuts table in CLAUDE.md
chore(ci): add release-please workflow
perf(search): use FTS5 trigram index for faster lookups
feat(ai)!: switch to streaming responses
BREAKING CHANGE: AI provider interface now requires stream() method
Create the commit using a HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
type(scope): description
EOF
)"
Push to the current branch with git push. If the branch has no upstream, use git push -u origin HEAD.
$ARGUMENTS