القائمة
Any time committing, pushing, or creating new revisions is mentioned, use this commit flow.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Lint prose against Simplified Technical English (ASD-STE100) rules. Use when the user asks to check, lint, or simplify technical writing (specs, manuals, procedures, docs) for STE compliance, or mentions ASD-STE100 or Simplified Technical English.
Step-by-step procedure for building a Claude Code channel integration. Use when creating a new channel plugin that connects Claude Code to external systems via MCP, named pipes, webhooks, or chat platforms.
This skill should be used when the user asks to "set up a dev environment", "create a workspace", "open a browser pane", "split terminal", "spin up frontend and backend", "use cmux", "manage cmux panes", "run commands in cmux", or mentions cmux workspaces, panes, surfaces, or browser automation. Provides workflow guidance for orchestrating multi-pane development environments with terminal and browser surfaces.
Use when merging a stack of stacked PRs with jj. Triggered by phrases like "merge the PR stack", "merge the stacked PRs", "land these PRs", or "merge the stack into main".
Use when addressing PR review comments on stacked jj branches. Triggered by phrases like "address review comments", "fix PR feedback", "respond to review on stacked branch", or "update the PR with reviewer suggestions".
Use when writing python code. Can be used for code review.
| name | Committing |
| description | Any time committing, pushing, or creating new revisions is mentioned, use this commit flow. |
You are staff engineer committing a commit message.
Check for jj - Use that by default.
jj commits all files by default (no staging step needed).jj describe -m "<message>" && jj new if you're on a revision with changesIf the working copy has changes that belong to different commits, use jj split:
JJ_EDITOR=true jj split <filesets> — files matching the filesets go in the first revision, the rest in the second.jj describe -r <rev-id> -m "message" for each resulting revision.Commit message format:
Under 50 lines
Brief but descriptive
After jj git push, always run jj new to start a fresh empty revision. Never leave the working copy on a revision that was just pushed.
When jj git push fails with "stale info" or "references unexpectedly moved on the remote", read resources/jj-stale-remote-push.md for the fix procedure.