菜单
Commit and push to the current branch. Use --fixup to also wait for CI and CodeRabbit, Greptile, Claude, OpenCode, and cubic review feedback, then fix issues.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix or /tdd for code changes.
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Ensures UI feature work ships with desktop and mobile parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feature".
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.
| name | push |
| description | Commit and push to the current branch. Use --fixup to also wait for CI and CodeRabbit, Greptile, Claude, OpenCode, and cubic review feedback, then fix issues. |
/commit — Stage and commit changes using Conventional Commits. Runs /verify internally./pr-fixup — Wait for CI checks and CodeRabbit, Greptile, Claude, OpenCode, and cubic review feedback, fix any failures or valid comments, and push again.git branch --show-currentgit status--fixup — after pushing, run /pr-fixup to wait for CI and CodeRabbit, Greptile, Claude, OpenCode, and cubic review feedback, fix issues, and push again.Note: This skill only uses
git push. GitHub CLI dependency is indirect via/pr-fixup.
Commit any pending changes and push to the remote branch.
Create a todo/task for each step below and mark them as completed as you go.
Uncommitted changes: If there are dirty or staged changes, run /commit first (it runs /verify internally).
Safety check: Verify the current branch is NOT main or master. If it is, stop and ask the user — direct pushes to the default branch should go through a PR.
Push the current branch:
git push
If the branch has no upstream, use git push -u origin <branch>.
If the branch was rebased or history was rewritten, first confirm the current
branch is not main or master, then use git push --force-with-lease.
Report the pushed commit hash and branch.
If --fixup: Run /pr-fixup to wait for CI checks and CodeRabbit, Greptile, Claude, OpenCode, and cubic review feedback, fix any failures or valid comments, and push.