- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill code-overview-to-confluence -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill code-overview-to-confluence -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill code-overview-to-confluence -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add testdouble/han --skill code-overview-to-confluence -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/testdouble/han/tree/HEAD/han-atlassian/skills/code-overview-to-confluenceDo publicador
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
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, which governs precedence
between 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
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 publishes that one file as a single Confluence page — the single-page sibling of
han-atlassian:investigate-to-confluence and han-atlassian:project-documentation-to-confluence, not the
parent-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
tools itself; han-atlassian:markdown-to-confluence owns all of that.
Confirm the skill has everything it needs before spending effort on an overview:
mcp__claude_ai_Atlassian__getAccessibleAtlassianResources to
confirm the server is connected and retrieve the cloud ID(s). If the tool is not available, the call errors, or it
returns no accessible resources (typically an authentication or configuration problem), stop immediately. Tell
the user this skill requires the Atlassian MCP server to be installed, configured, and authenticated, and that they
can re-run it once it is connected. Do not fall back to a local-only run; for a local-only overview, point them at
han-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
forwarded to han-coding:code-overview verbatim in Step 2. A target is not required: with none given,
han-coding:code-overview defaults to the current branch's changes. Do not resolve or classify the target here; that
is han-coding:code-overview's job.AskUserQuestion, explaining plainly that the skill needs an exact destination because it
does not search Confluence. Do not resolve the page tree here — only confirm a location was given. Carry it through
to 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
target (file, directory, symbol, or PR reference, or none for the current branch's changes), any size the user gave, and
the relevant conversation context. Do not summarize, trim, or reinterpret the user's context; pass it through so
han-coding:code-overview runs exactly as it would on its own (target resolution, mode and size selection, parallel
han-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 —
except add one explicit instruction: it must write the overview to an explicit scratch path this skill names (for
example ${TMPDIR:-/tmp}/code-overview-<slug>.md). Passing the path explicitly keeps the file where this skill expects
it even when either .han/config.md configures an output directory, because explicit input outranks the config
(see ../../references/config-rule.md). Capture the exact scratch-file path it
wrote. 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 whether to publish. State plainly that the content has not been published anywhere yet, and that no code was changed.
Publishing to Confluence puts the content where other people can see it, so require an explicit choice before posting.
Ask with AskUserQuestion, restating the scratch-file path and the Confluence destination the user provided.
Offer 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 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:
draft or live), stated explicitly so
han-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
mode, handles Mermaid diagrams, and reports the resulting page URL. Relay its result to the user: the created or updated
page's URL and whether it went live or was saved as a draft. If publishing fails, report the error and confirm the
scratch-file markdown is unchanged and intact.
han-coding:code-overview ran with the full forwarded context, wrote the
overview to a scratch file whose path was captured, and changed no code.han-atlassian:markdown-to-confluence created or
updated the page in the chosen mode and its URL was relayed; when the user declined, only the scratch file exists.>
---name: code-overview-to-confluencedescription: >---# han-atlassian/skills/code-overview-to-confluence/SKILL.mdPerguntas frequentes
Baixe han-atlassian/skills/code-overview-to-confluence/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/testdouble/han.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.