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 an evidence-based investigation with the core han-coding:investigate skill, lets the user review the\nresulting report, and then publishes it to a Confluence location that the user must specify. It is a thin\norchestrator: the investigation work belongs to han-coding:investigate, and the publishing work belongs to\nhan-atlassian:markdown-to-confluence. This skill only validates its inputs, runs the investigation to a temporary\nfile, gets the user's review and publish choice, and hands the file to the publisher.
han-coding:investigate produces a single report file (the investigation plan: problem statement, evidence summary,\nroot cause analysis, planned fix, validation results, and summary). It does not produce companion artifacts, so this\nskill publishes that one file as a single Confluence page — the single-page sibling of\nhan-atlassian:project-documentation-to-confluence, not the parent-plus-children tree of\nhan-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 investigation:
\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 investigation, point them\nat han-coding:investigate. This preflight runs first so a missing server fails before any investigation work\nbegins.han-coding:investigate verbatim in Step 2. If the request is too thin to start, let han-coding:investigate run\nits own investigation rather than pre-empting it here.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:investigate skill with the Skill tool, forwarding all provided context verbatim: the\nsymptom or question, any known reproduction steps or error messages, any suspected entry points, and the relevant\nconversation context. Do not summarize, trim, or reinterpret the user's context; pass it through so\nhan-coding:investigate runs exactly as it would on its own (parallel investigators, conditional specialist analysts,\nadversarial validation, and the final report) — except add two explicit instructions:
/tmp/ (for example /tmp/<symptom-slug>.md) rather\nthan into the project's docs or plans directory. This keeps the working report out of the repo until the user decides\nto publish it, and because the path is explicit input it outranks any output-directory the project or personal\n.han/config.md supplies (see ../../references/config-rule.md).han-coding:investigate normally ends by presenting the plan for\napproval and can trigger the fix's implementation on approval; this skill wants the report only, so instruct it not to\nimplement the fix or change any code — this skill publishes findings, it does not ship them.Let han-coding:investigate complete its full investigation process. Capture the exact /tmp/ file path it wrote.\nThat markdown file is the source content for Confluence. Proceed to Step 3 once it finishes.
Tell the user the exact /tmp/ path of the generated investigation report so they can open and review it before\ndeciding whether to publish. State plainly that the content has not been published anywhere yet, and that no code was\nchanged.
Publishing to Confluence puts the content where other people can see it, so require an explicit choice before posting.\nAsk with AskUserQuestion, restating the /tmp/ 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 /tmp/ report path and state clearly that nothing was published\nto Confluence. Otherwise, record the chosen publish mode (draft or live) for Step 5.
Invoke the han-atlassian:markdown-to-confluence skill with the Skill tool, forwarding:
/tmp/ markdown file path captured in Step 2,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\n/tmp/ markdown file is unchanged and intact.
han-coding:investigate ran with the full forwarded context, wrote the investigation\nreport to a /tmp/ file whose path was captured, and did not implement the fix or change any code./tmp/ path was shown to the user before any publish.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 /tmp/ report exists.