Agent skill
jj-context
Show current commit status and changes from trunk in jj
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/jj-context
SKILL.md
/jj-context - Show Current Context
Display the current jj working copy status and all changes from trunk.
Instructions
-
Show current status: Run
jj statusto see the current working copy status, including:- Modified files in the working copy
- The current commit's parent(s)
- Any conflicts
-
Show commits from trunk: Run
jj log -r 'trunk()..@'to see all commits between trunk and the current working copy. This shows the commit history of your current work. -
Get change overview: Run these commands to understand the scope of changes from trunk:
jj diff -r 'trunk()..@' --summary- List of files with change type (modified/added/deleted)jj diff -r 'trunk()..@' --stat- Histogram showing lines changed per file
-
Analyze the changes:
- For small changes (≤10 files, ≤300 lines total): Run
jj diff -r 'trunk()..@'directly to see the full diff - For large changes (>10 files or >300 lines): Use the Task tool with
subagent_type=Exploreto analyze:prompt: "Run `jj diff -r 'trunk()..@'` and provide a structured summary: 1) Group changes by directory/subsystem 2) Describe the key modifications in each area 3) Note any significant additions or deletions. Keep each section brief."
- For small changes (≤10 files, ≤300 lines total): Run
-
Present the context: Display to the user:
- Current status
- Commit log from trunk
- Files changed summary (from --summary)
- For small diffs: the actual diff; for large diffs: the Task agent's summary
Notes
trunk()in jj refers to the main branch (typicallymainormaster)- The
..range includes all commits between the two revisions - This is useful for understanding the full scope of work before creating a PR or reviewing changes
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?