code-overview-to-confluence

## Project Context - 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. # Code Overview to Confluence This skill runs a progressive-disclosure code overview with the core `han-coding:code-overview` skill, lets the user review the resulting overview, and then publishes it to a Confluence location that **the user must specify**. It is a thin orchestrator: the overview work belongs to `han-coding:code-overview`, and the publishing work belongs to `han-atlassian:markdown-to-confluence`. This skill only validates its inputs, runs the overview to a scratch file, gets the user's review and publish choice, and hands the file to the publisher. `han-coding:code-overview` produces a **single** scratch file (the overview: what the code does, how it flows, where to start, and — in PR mode — what changed and what to watch when reviewing). It does not produce companion artifacts, so this skill publish...