update-pr-description

## Pre-requisites - gh CLI: !`which gh 2>/dev/null || echo "not installed"` **If the gh CLI is not found:** - Inform the user that it needs to be installed and configured before this skill can be used - **Immediately stop** execution of this skill, as it cannot be executed ## Project Context - current branch: !`git branch --show-current 2>/dev/null || echo unknown` - default branch: !`git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo unknown` - branch summary: !`git log origin/HEAD..HEAD --oneline 2>/dev/null || echo unknown` - branch stats: !`git diff origin/HEAD...HEAD --stat 2>/dev/null || echo unknown` - branch changes: !`git diff origin/HEAD...HEAD 2>/dev/null || echo unknown` - personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"` - project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""` As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md` probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence between the two files, relative-path resolution, and what to do with a file that reads but cannot be used. ## Step 1: Validate Branch State Before generating a PR description, verify the branch has content to describe: 1. **If `default br...