메뉴
Start work on a new issue or feature by creating a jj change on the up-to-date default branch with an optional named bookmark.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill when managing packages, external dependencies, binaries, or CLI tools in a chezmoi dotfiles repository. Handles adding/updating/removing packages in .chezmoidata/packages.yaml, creating .chezmoiexternals/ organized files, pinning versions with Renovate automation, and selecting the correct package ecosystem (Homebrew, mise, Python, Docker, chezmoi externals).
Write, debug, and optimize custom GLSL shaders for the Ghostty terminal. Covers Ghostty's Shadertoy-compatible GLSL ES 3.0 dialect, its terminal-specific uniforms (cursor position and color, focus state, event timestamps), the unsupported Shadertoy uniforms, focus-gated performance patterns, and adapting shaders from shadertoy.com. Use when creating or editing a .glsl file for Ghostty, diagnosing a shader that renders black or fails to compile, or setting custom-shader config.
Reference for deeper Jujutsu (jj) topics beyond the everyday describe/advance workflow. Load when working with conflicts, the operation log, bookmarks, revsets, fork/PR workflows, colocated Git repos, multi-remote setups, divergent changes, or jj config. Also the place to look up fileset glob syntax, non-interactive `jj split`, and bookmark advancement.
Describe and finalize work with jj-vcs — drafting a description for the current change, splitting mixed work into focused commits, and advancing to a clean working copy. Use when asked to commit, when finishing a unit of work, or when starting new work on top of undescribed changes.
Build comprehensive understanding of a problem by gathering context from GitHub issues, codebase exploration, git history, and linked references. Use when starting work on an issue or investigating a problem.
Design an implementation as a task graph with explicit dependencies, parallel phases, and agent team topology. Use after gathering context and agreeing on an approach, when the work is large enough that sequencing it badly costs real time.
| name | checkout |
| description | Start work on a new issue or feature by creating a jj change on the up-to-date default branch with an optional named bookmark. |
$ARGUMENTS
Working copy: !`jj log -r @ --no-graph -T 'change_id.shortest() ++ " " ++ if(description, description.first_line(), "(no description)")' 2>/dev/null`
Working copy empty: !`jj diff --stat 2>/dev/null | head -1`
Log: !`jj log -r 'ancestors(@, 5)' --no-graph -T 'change_id.shortest() ++ " " ++ bookmarks ++ " " ++ if(description, description.first_line(), "(empty)") ++ "\n"' 2>/dev/null`
Determine what $ARGUMENTS contains:
| Pattern | Action |
|---|---|
#123 or issue URL | Fetch issue title, derive bookmark name |
Bookmark name (e.g., feat/dark-mode) | Use directly |
| Empty | Ask what to work on |
If $ARGUMENTS is an issue reference:
gh issue view <number> --json number,title,labelsfix/, feature labels → feat/, chore/maintenance labels → chore/, default → feat/)<prefix><number>-<kebab-case-title> (e.g., feat/123-add-dark-mode)Check pre-computed context for the current working copy state.
In jj, the working copy @ is always a change being edited. Before starting new work, assess:
| Situation | Action |
|---|---|
| Working copy is empty (no diff) | Safe to proceed — jj new will leave an empty change behind (auto-abandoned) |
| Working copy has changes with a description | Suggest jj commit first to finalize, then proceed |
| Working copy has changes without a description | Suggest jj commit -m "..." or jj describe -m "..." first |
Conflicts exist (jj st shows conflicts) | Inform user and wait for guidance |
Do not silently abandon or squash work.
jj git fetch — ensure we have latest from remotejj new main -m "<issue title or description>"
jj bookmark create <bookmark-name> -r @
Report the change ID, bookmark name, and parent (e.g., Created change xyz on bookmark feat/123-add-dark-mode from main), then immediately mark this task complete and execute the next task in the workflow.