bash \"${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh\" 2>/dev/null || echo \"$HOME/.claude\"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\nthat returns no file is no personal configuration: continue silently. When that file or the project .han/config.md\nprobe supplies content, apply it per config-rule.md, which governs precedence\nbetween the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
This skill runs a progressive-disclosure code overview with the core han-coding:code-overview skill, lets the user\nreview the resulting overview, and then publishes it to a Confluence location that the user must specify. It is a\nthin orchestrator: the overview work belongs to han-coding:code-overview, and the publishing work belongs to\nhan-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the overview to a scratch file, gets\nthe 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\nstart, and — in PR mode — what changed and what to watch when reviewing). It does not produce companion artifacts, so\nthis skill publishes that one file as a single Confluence page — the single-page sibling of\nhan-atlassian:investigate-to-confluence and han-atlassian:project-documentation-to-confluence, not the\nparent-plus-children tree of han-atlassian:plan-a-feature-to-confluence.
The five steps below are the whole skill. It does not resolve Confluence pages or call the Confluence MCP create/update\ntools itself; han-atlassian:markdown-to-confluence owns all of that.
Confirm the skill has everything it needs before spending effort on an overview:
\nmcp__claude_ai_Atlassian__getAccessibleAtlassianResources to\nconfirm the server is connected and retrieve the cloud ID(s). If the tool is not available, the call errors, or it\nreturns no accessible resources (typically an authentication or configuration problem), stop immediately. Tell\nthe user this skill requires the Atlassian MCP server to be installed, configured, and authenticated, and that they\ncan re-run it once it is connected. Do not fall back to a local-only run; for a local-only overview, point them at\nhan-coding:code-overview. This preflight runs first so a missing server fails before any overview work begins.small, medium, or large). All of this — together with the relevant conversation context — is\nforwarded to han-coding:code-overview verbatim in Step 2. A target is not required: with none given,\nhan-coding:code-overview defaults to the current branch's changes. Do not resolve or classify the target here; that\nis han-coding:code-overview's job.AskUserQuestion, explaining plainly that the skill needs an exact destination because it\ndoes not search Confluence. Do not resolve the page tree here — only confirm a location was given. Carry it through\nto Step 5; han-atlassian:markdown-to-confluence resolves it.Invoke the han-coding:code-overview skill with the Skill tool, forwarding all provided context verbatim: the\ntarget (file, directory, symbol, or PR reference, or none for the current branch's changes), any size the user gave, and\nthe relevant conversation context. Do not summarize, trim, or reinterpret the user's context; pass it through so\nhan-coding:code-overview runs exactly as it would on its own (target resolution, mode and size selection, parallel\nhan-core:codebase-explorer exploration, synthesis, and the readability-review pass).
han-coding:code-overview already writes its overview to a scratch file outside the repository and changes no code —\nexcept add one explicit instruction: it must write the overview to an explicit scratch path this skill names (for\nexample ${TMPDIR:-/tmp}/code-overview-<slug>.md). Passing the path explicitly keeps the file where this skill expects\nit even when either .han/config.md configures an output directory, because explicit input outranks the config\n(see ../../references/config-rule.md). Capture the exact scratch-file path it\nwrote. That markdown file is the source content for Confluence. Proceed to Step 3 once it finishes.
Tell the user the exact scratch-file path of the generated overview so they can open and review it before deciding\nwhether to publish. State plainly that the content has not been published anywhere yet, and that no code was changed.
\nPublishing to Confluence puts the content where other people can see it, so require an explicit choice before posting.\nAsk with AskUserQuestion, restating the scratch-file path and the Confluence destination the user provided.\nOffer three options, listing the draft option first as the recommended default:
If the user keeps it local only, stop. Report the scratch-file path and state clearly that nothing was published to\nConfluence. Otherwise, record the chosen publish mode (draft or live) for Step 5.
\nInvoke the han-atlassian:markdown-to-confluence skill with the Skill tool, forwarding:
draft or live), stated explicitly so\nhan-atlassian:markdown-to-confluence does not re-ask.han-atlassian:markdown-to-confluence resolves the location, reads the file, creates or updates the page in the chosen\nmode, handles Mermaid diagrams, and reports the resulting page URL. Relay its result to the user: the created or updated\npage's URL and whether it went live or was saved as a draft. If publishing fails, report the error and confirm the\nscratch-file markdown is unchanged and intact.
han-coding:code-overview ran with the full forwarded context, wrote the\noverview to a scratch file whose path was captured, and changed no code.han-atlassian:markdown-to-confluence created or\nupdated the page in the chosen mode and its URL was relayed; when the user declined, only the scratch file exists.