Teach commit and PR skills about workflow and context linking
Assisted-by: Claude Opus 4.6 via Claude Code
diff --git a/ai/claude/skills/gh-pr/SKILL.md b/ai/claude/skills/gh-pr/SKILL.md
index f9039bbd..3469b972 100644
--- a/ai/claude/skills/gh-pr/SKILL.md
+++ b/ai/claude/skills/gh-pr/SKILL.md
@@ -55,6 +55,9 @@ Revision must be provided (bookmark, change ID, revset, or commit hash). The rev
- Explain user-facing impact, architectural decisions, and tradeoffs
- If design decisions were found in episodic memory, include a "Design Decisions"
section highlighting key choices and their rationale
+ - If the session references a blocking PR, linked issue, Slack thread,
+ or other related context, include it in the description automatically
+ (e.g., "Depends on #123", "Closes #456", or a Slack permalink)
- Never wrap commit SHAs or PR/issue numbers in backticks—GitHub
auto-links raw `a1b2c3d` and `#123` but backticks prevent it
- Follow repository conventions
diff --git a/ai/claude/skills/jj-commit/SKILL.md b/ai/claude/skills/jj-commit/SKILL.md
index 306fb81e..233058a7 100644
--- a/ai/claude/skills/jj-commit/SKILL.md
+++ b/ai/claude/skills/jj-commit/SKILL.md
@@ -7,6 +7,12 @@ allowed-tools: Bash(jj diff:*) Bash(jj show:*) Bash(jj log:*)
# Commit Changes
+## Workflow
+
+Execute directly without exploring the codebase first. When asked to
+commit and create a PR, use this skill followed by the `/pr` skill
+unless told otherwise.
+
## Fileset (optional)
`$ARGUMENTS`