القائمة
REQUIRED for version control work in repositories containing .jj/. If .jj/ exists, use jj only and never git. Trigger on commit, status, diff, show, log, history, or any VCS request.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
REQUIRED for end-user customization of Linux desktop, window manager, or system config. Use when editing ~/.config/hypr/, ~/.config/waybar/, ~/.config/walker/, ~/.config/alacritty/, ~/.config/kitty/, ~/.config/ghostty/, ~/.config/mako/, or ~/.config/omarchy/. Triggers: Hyprland, window rules, animations, keybindings, monitors, gaps, borders, blur, opacity, waybar, walker, terminal config, themes, wallpaper, night light, idle, lock screen, screenshots, layer rules, workspace settings, display config, and user-facing omarchy commands. Excludes Omarchy source development in ~/.local/share/omarchy/ and omarchy-dev-* workflows.
REQUIRED when the user explicitly says "buddy", "task-buddy", or "verify-buddy" (or plurals "buddies", "task-buddies", "verify-buddies", and close variants like "use buddy", "run a task-buddy", "do a verify-buddy", "run 4 verify-buddies"). Do not trigger on generic phrases like "second opinion", "external review", "another model", or "GPT" -- only on the literal terms buddy / task-buddy / verify-buddy (and their plurals).
Conventions for creating or modifying personal scripts in ~/workspace/conf/bin. Trigger when adding, editing, or discussing scripts in the bin directory.
Create, refine, review, merge, and archive project plan files. Use when the task is about planning work, naming plan files, creating new plan documents under ./plan, or archiving completed plans into ./plan-archive.
Prompt template for exploring open-source code (extracted from paint/note). User will refine later.
Prompt template for exploring open-source code (extracted from paint/note). User will refine later.
| name | jujutsu |
| description | REQUIRED for version control work in repositories containing .jj/. If .jj/ exists, use jj only and never git. Trigger on commit, status, diff, show, log, history, or any VCS request. |
| allowed-tools | Bash(jj *) |
Use this skill whenever version control is involved in a repository with .jj/.
.jj/ exists, never run git commands.jj commands only.jj desc -m "...".This workflow is intentionally simple:
jj stjj desc -m "..."jj diffjj logjj show or jj show <revset>jj new (allways ask)jj st - statusjj log - historyjj diff - current change diffjj show - details for current changejj show <revset> - details for a specific revisionjj desc -m "..." - set change descriptionjj new - start a new changeRevsets are jj's revision query language. They let you select exactly which
changes commands should operate on. A common use is filtering history with
jj log -r <revset>.
Examples:
jj log -r @ - show current change
jj log -r @- - show parent of current change
jj log -r 'root()..@' - show ancestors up to current change (excluding root())
jj log -r 'heads(all())' - show all heads
@ - current working-copy change
@- - parent of current change
@+ - children of current change
root()..@ - ancestors up to current change
heads(all()) - all heads
bookmarks() - all bookmarked revisions
main - revision pointed to by local main
main@origin - remote main on origin