菜单
Prepare code for commit with quality checks and conventional commit message generation. Use when the user asks to prepare a commit, review changes before committing, or wants a thorough pre-commit check including lint, tests, and code review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create a demo user and company on local Panda via curl. Authenticates against the local dev server, submits the demo account form, and returns login credentials. Use when the user asks to create a local user, demo account, demo company, or needs a test account on local Panda.
Publish implementation plans to Notion instead of local markdown. Use whenever creating an implementation plan, architecture plan, spike plan, migration plan, or any planning document. Replaces local docs/ output with a Notion page under the Planning docs page.
List and remove old git worktrees sorted by last activity. Shows when each worktree was last touched and lets the user pick which ones to remove. Also cleans up the associated local branch and AVD emulator if one exists. Use when the user says "cleanup worktrees", "remove worktrees", "delete old worktrees", "clean up branches", or "list worktrees".
Delete all Android emulators created by the build-android-app skill. Finds AVDs matching the {project}_{branch} naming convention, shuts down any that are running, and deletes them. Use when the user says "cleanup emulators", "delete emulators", "remove avds", or "clean up android emulators".
Build, install, and launch an Android app on an emulator after code changes. Auto-detects Gradle wrapper, build variant, application ID, and emulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on emulator", or when a workspace rule says to build after changes.
Build, install, and launch an iOS app on the Simulator after code changes. Auto-detects project file, scheme, bundle ID, and simulator. Use after making code changes to verify compilation, when the user says "build the app", "run the app", "launch on simulator", or when a workspace rule says to build after changes.
| name | dev-workflow-prepare-commit |
| description | Prepare code for commit with quality checks and conventional commit message generation. Use when the user asks to prepare a commit, review changes before committing, or wants a thorough pre-commit check including lint, tests, and code review. |
Thoroughly prepare and validate changes before creating a commit.
git status
If there are unstaged changes:
ALWAYS use the AskQuestion tool to prompt the user. Show the user which files are unstaged, then use AskQuestion:
Based on the response:
git add -A then continuegit diff --staged
Review all staged changes and check for:
console.log, debugger, or commented-out code that shouldn't be committedIf issues are found:
Categorize issues by severity:
Report each issue clearly with file, line reference, and severity.
For critical issues only:
ALWAYS use the AskQuestion tool:
Do NOT offer "Proceed anyway" for critical issues.
Based on the response:
For minor issues only (or after critical issues are resolved):
ALWAYS use the AskQuestion tool:
Based on the response:
npm run lint
If lint errors exist:
ALWAYS use the AskQuestion tool:
Based on the response:
npm run lint -- --fix and re-checkUse the unit-test-runner subagent to run tests, or run directly:
npm test
If tests fail:
ALWAYS use the AskQuestion tool:
Do NOT proceed with failing tests unless explicitly overridden by the user.
Based on the response:
Analyze the staged changes to create a conventional commit message.
git diff --staged --stat
git diff --staged
Conventional Commits Format:
<type>: <short description>
Types:
| Type | Use For |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, no code change |
refactor | Code change that neither fixes nor adds |
perf | Performance improvement |
test | Adding or fixing tests |
chore | Build, config, or tooling changes |
Guidelines:
header-max-length)feat(auth):, just feat:)Co-authored-by: lines of any kindExamples:
refactor: migrate queries to suspensefeat: add dark mode togglefix: resolve login redirect loopALWAYS use the AskQuestion tool to present the generated commit message:
Based on the response:
Execute the commit:
CRITICAL: NO CO-AUTHOR TRAILERS
Do NOT add any
Co-authored-bytrailers to the commit. The commit message must contain ONLY the type and short description - nothing else. No trailers, no co-author attribution, no additional metadata.
git commit -m "<type>: <short description>"
-m flag--trailer--authorCo-authored-by: lines<type>: <short description>Verify success:
git status
git log -1 --oneline
Confirm the commit was created successfully.
After a successful commit, ALWAYS use the AskQuestion tool:
Based on the response:
git push and confirm successIf pushing:
git push
Confirm the push was successful and show the remote branch status.
Stop the workflow immediately if: