New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Code Overview To Confluence

by testdouble in testdouble/han

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location.

MITAuto-check passedDevelopment

Install Code Overview To Confluence

skills CLI
$ npx skills add testdouble/han --skill code-overview-to-confluence -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install testdouble/han code-overview-to-confluence --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/testdouble/han.git skills-src && mkdir -p .claude/skills && cp -r skills-src/han-atlassian/skills/code-overview-to-confluence .claude/skills/code-overview-to-confluence && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
code-overview-to-confluence
GitHub stars
279
Token cost
~2.3k tokens
SKILL.md length
1,111 words
Files
1
Skills in repo
54
Repo updated
First seen
Licence
MIT

At a glance

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location.

  • Works in 5 steps: Validate Inputs → Produce the Overview to a Scratch File → Show the File for Review → …
  • The user wants code
  • SKILL.md covers Project Context, Step 1: Validate Inputs, Step 2: Produce the Overview… and Step 3: Show the File for Review, plus 3 more sections
  • Calls bash

What it does

Code Overview To Confluence is an agent skill from testdouble/han. Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence…

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Markdown, Root cause analysis and Pull requests. It works with Confluence, Model Context Protocol and Jira. The repository describes itself as: Han: AI skills and agents for "Solo" product engineers and small teams. The licence is MIT.

When your agent uses it

  • The user wants code
  • Made sense of AND the overview posted to a Confluence space

Example prompts

  • “Use the code-overview-to-confluence skill to produce a progressive-disclosure overview of unfamiliar code or a pull request's changes with…”
  • “/code-overview-to-confluence”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Skill, Agent, Bash(find *), mcp__claude_ai_Atlassian__getAccessibleAtlassianResources, Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh")

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Validate Inputs
  2. Produce the Overview to a Scratch File
  3. Show the File for Review
  4. Confirm the Publish Choice
  5. Publish with markdown-to-confluence

What it can do on your machine

Read from SKILL.md and the folder at commit abba73a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Skill
    • Agent
    • Bash(find *)
    • mcp__claude_ai_Atlassian__getAccessibleAtlassianResources
    • Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh")

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Code Overview To Confluence loads about 2.3k tokens when it runs. Until then it costs about 215 tokens; SKILL.md has 1,111 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~215
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from testdouble/han at commit abba73a, republished under its MIT licence (© testdouble). 1,111 words, ~2,321 tokens.

Download SKILL.mdSave it as .claude/skills/code-overview-to-confluence/SKILL.md (or your agent's skills folder).
name
code-overview-to-confluence
description
Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not root-cause a bug to Confluence — use investigate-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.
allowed-tools
Read, Glob, Grep, Skill, Agent, Bash(find *), mcp__claude_ai_Atlassian__getAccessibleAtlassianResources, Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh")
argument-hint
[size: small | medium | large] [target: file, directory, symbol, or PR reference — defaults to the current branch's changes] [confluence location: page URL or…

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, 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 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.

Step 1: Validate Inputs

Confirm the skill has everything it needs before spending effort on an overview:

  1. Atlassian MCP reachable (hard requirement). Call 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.
  2. A target to overview (optional). The target may be a file, directory, symbol, or pull request reference, and an optional size (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.
  3. A Confluence destination. Confirm the request provides a target location: a Confluence page URL (to update that page, or create a child under it), or a space (key or name) plus an optional parent page. If none was provided, ask for one with 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.

Step 2: Produce the Overview to a Scratch File

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.

Show full SKILL.md (423 more words)Show less

Step 3: Show the File for Review

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.

Step 4: Confirm the Publish Choice

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:

  • "Yes, save it as a draft to edit later (recommended)" — published as an unpublished Confluence draft for the user to review, edit, and publish themselves. This is the default. (Publish mode: draft.)
  • "Yes, publish it live now" — the page goes live immediately. (Publish mode: live.)
  • "No, keep it local only" — nothing is published.

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.

Step 5: Publish with markdown-to-confluence

Invoke the han-atlassian:markdown-to-confluence skill with the Skill tool, forwarding:

  • the scratch-file markdown path captured in Step 2,
  • the Confluence destination the user provided in Step 1 (the page URL, or the space plus optional parent page), passed through verbatim, and
  • the publish mode the user chose in Step 4 (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.

Verification

  1. Inputs validated: the Atlassian server was reachable and a Confluence location was provided — or the skill stopped before doing any work.
  2. Overview produced to a scratch file: 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.
  3. User reviewed: the scratch-file path was shown to the user before any publish.
  4. Explicit choice obtained: the user chose draft, live, or local-only.
  5. Publish delegated and reported: when the user chose to publish, 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.

© testdouble, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in han-atlassian/skills/code-overview-to-confluence of testdouble/han.

Open the folder on GitHubat commit abba73a

Compare with similar skills

Code Overview To Confluence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Code Overview To Confluence compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Code Overview To Confluence this skilltestdouble/han279—~2.3kAutomated safety check: PassMIT
Link Ticket To SessionJayantDevkar/claude-code-karma329—~1.8kAutomated safety check: NotesApache-2.0
Review Release Noteschef/chef-web-docs143—~5.2kAutomated safety check: PassCustom licence
Prime Codebasecoleam00/skills670—~887Automated safety check: PassMIT
Prime Backendcoleam00/skills670—~1.1kAutomated safety check: PassMIT
Nightly Triageshopsys/shopsys350—~4.6kAutomated safety check: PassCustom licence

Similar skills

  • Link Ticket To Session

    JayantDevkar/claude-code-karma

    Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma.

    329 GitHub stars~1.8k tokensUpdated 8 days ago
    DevelopmentAuto-check: notes

  • Review Release Notes

    chef/chef-web-docs

    Read a release notes file and edit it using Jira release data and GitHub pull requests as co-equal, optional sources.

    143 GitHub stars~5.2k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Prime Codebase

    coleam00/skills

    Primes the agent with deep codebase understanding by analyzing structure, documentation, and key files.

    670 GitHub stars~887 tokensUpdated 20 days ago
    DevelopmentAuto-check passed

  • Prime Backend

    coleam00/skills

    Primes the agent with focused understanding of the backend portion of the codebase — API routes, services, data models, and database layer — without loading unrelated frontend code.

    670 GitHub stars~1.1k tokensUpdated 20 days ago
    Backend & APIsAuto-check passed

  • Nightly Triage

    shopsys/shopsys

    Triage of a failed nightly verification run — fix-first. An agent skill from shopsys/shopsys.

    350 GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Akb Ingest

    dnotitia/akb

    Ingest whatever you point at into an AKB vault — a local file, a web URL, a GitHub PR/release/commit, a Confluence page, or a Jira issue.

    161 GitHub stars~2k tokensUpdated today
    Agent WorkflowsAuto-check passed

More from testdouble/han

All 54 skills in this repo

  • HTML Summary

    testdouble/han

    Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived…

    279 GitHub stars~2.9k tokensUpdated 6 days ago
    Auto-check passed

  • Han Update Documentation

    testdouble/han

    Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate.

    279 GitHub stars~3.4k tokensUpdated 6 days ago
    Auto-check passed

  • Guidance

    testdouble/han

    Authoritative guidance for building Claude Code skills, agents, and plugins, plus init and update steps that install and refresh the plugin-building skills in the current repository.

    279 GitHub stars~1.8k tokensUpdated 6 days ago
    Auto-check passed

  • Han Release

    testdouble/han

    Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve…

    279 GitHub stars~8.6k tokensUpdated 6 days ago
    Auto-check passed

  • Plan Implementation

    testdouble/han

    Builds a feature implementation plan from an existing feature specification (or equivalent context) through a facilitated team conversation.

    279 GitHub stars~9.5k tokensUpdated 6 days ago
    Auto-check passed

  • Refactor

    testdouble/han

    Restructure existing code without changing its behavior, through a test-gated refactoring loop: a named target, a green suite over that target before any edit, a planned sequence of small named…

    279 GitHub stars~3.1k tokensUpdated 6 days ago
    Auto-check passed

Works with

Categories

Questions about Code Overview To Confluence

What does Code Overview To Confluence do?

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Code Overview To Confluence is an agent skill from testdouble/han. Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location.

When should I use Code Overview To Confluence?

Code Overview To Confluence fits situations like: the user wants code; made sense of AND the overview posted to a Confluence space.

How do I install Code Overview To Confluence in Claude Code?

Run `npx skills add testdouble/han --skill code-overview-to-confluence -a claude-code`. Or copy the skill folder (han-atlassian/skills/code-overview-to-confluence in testdouble/han) into .claude/skills/code-overview-to-confluence in your project. Claude Code loads it when a task matches its description.

How do I install Code Overview To Confluence in Codex?

Run `npx skills add testdouble/han --skill code-overview-to-confluence -a codex`. Or copy the skill folder (han-atlassian/skills/code-overview-to-confluence in testdouble/han) into .agents/skills/code-overview-to-confluence in your project. Codex loads it when a task matches its description.

Can I use Code Overview To Confluence in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add testdouble/han --skill code-overview-to-confluence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-overview-to-confluence, .gemini/skills/code-overview-to-confluence, .github/skills/code-overview-to-confluence and .opencode/skills/code-overview-to-confluence in your project.

What does Code Overview To Confluence need to run?

Going by SKILL.md and its folder, Code Overview To Confluence needs the command-line tools its instructions call (bash). Its frontmatter pre-approves these tools: Read, Glob, Grep, Skill, Agent, Bash(find *), mcp__claude_ai_Atlassian__getAccessibleAtlassianResources, Bash(bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh").

Does Code Overview To Confluence access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Code Overview To Confluence safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Code Overview To Confluence use?

Code Overview To Confluence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Code Overview To Confluence use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Code Overview To Confluence?

Skills that share tags, products or a category with Code Overview To Confluence: Link Ticket To Session (JayantDevkar/claude-code-karma, 329 stars), Review Release Notes (chef/chef-web-docs, 143 stars), Prime Codebase (coleam00/skills, 670 stars) and Prime Backend (coleam00/skills, 670 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Code Overview To Confluence?

testdouble (a GitHub organization) maintains it in testdouble/han, which has 279 GitHub stars. The repository holds 54 skills in this directory. The repository was last updated on October 1, 2026.

Source: testdouble/han on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.