Menu
Standard git workflow for handling changes on the current branch - add, commit, push, then auto-run MR generation when needed
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Select and run proportionate validation for changes to apps/canvas-workspace. Use when iterating on Canvas Workspace code, finishing a feature or fix, preparing release evidence, or deciding whether a full performance report is necessary.
Deep-research a topic and build a structured Pulse Canvas workspace with approved research depth, source-backed findings, progressive or final canvas creation, spatially organized frames, content nodes, and connections. Use when the user asks to bootstrap, generate, research, organize, or build an AI-created canvas.
Extend an existing Pulse Canvas frame with local, source-backed research while preserving the surrounding canvas. Use when the user asks to research, enrich, expand, verify, update, or add sources/details inside a selected or named frame, rather than bootstrapping a whole new canvas.
Operate Pulse Canvas workspaces — read user-curated context, write results, create nodes
Add or change a Pulse Canvas capability that must be available through structured agent tools and the pulse-canvas CLI. Use for cross-workspace Capability Runtime changes spanning apps/canvas-workspace, packages/canvas-cli, or packages/cli, including new live read, operate, or unsafe application actions.
Run the canvas-workspace performance evaluation, publish the latest static dashboard through the local nginx/Cloudflare Tunnel route, capture a screenshot, and summarize the report. Use when the user asks to run Pulse Canvas/canvas-workspace perf checks, deploy the performance dashboard, refresh https://jasperhu.art/apps/canvas-perf/, or send a dashboard screenshot from Feishu/remote-server.
| name | git-workflow |
| description | Standard git workflow for handling changes on the current branch - add, commit, push, then auto-run MR generation when needed |
| description_zh | Standard git workflow on current branch with auto MR generation after push when needed. |
| version | 1.6.0 |
| author | Pulse Coder Team |
This skill provides a streamlined git workflow for handling changes on the current branch without creating a new branch.
git status
Review the branch state and identify:
git add -A
Default behavior:
git add -Agit add <specific-files> only when the user explicitly asks for partial commitsImportant:
git commit only includes staged contentgit commit -m "<type>: <short description>"
Recommended commit message format:
<type>: <short description>
- <detail 1>
- <detail 2>
Common types:
feat - new featurefix - bug fixrefactor - refactordocs - documentationstyle - formatting/style onlytest - testschore - tooling/build/maintenancegit push
mr-generatorAfter a successful git push, if the current branch is not master or main and there is no existing open PR for this branch, run the mr-generator skill by default.
mr-generatormaster or main: skip mr-generatorSuggested message:
No open PR found for this branch. Running mr-generator by default.
mr-generator does not create MR automaticallyIf mr-generator is in preview mode or unable to create, show the generated title/description and stop.
# End-to-end quick run
git status
git add -A
git commit -m "Describe your changes"
git push
# Then run mr-generator if needed
git add src/ docs/
git commit -m "feat: update core feature and docs"
git push
git add src/app.ts
git commit -m "feat: add new feature"
git add tests/
git commit -m "test: add corresponding tests"
git push
After each run, verify:
git status - working tree is cleangit log --oneline -3 - latest commits look correctgit branch - current branch is expectedgit push, confirm whether MR creation flow (mr-generator) is needed