code-overview-to-confluence

Name: code-overview-to-confluence
Author: testdouble

122stars12forks

How to install code-overview-to-confluence?

testdouble/han/code-overview-to-confluence

$npx -y skills add testdouble/han --skill code-overview-to-confluence

Installs into the current project.

Summary

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 p

Files · 1

View on GitHub

SKILL.md

1	# Code Overview to Confluence
2
3	This skill runs a progressive-disclosure code overview with the core
4	`han-coding:code-overview` skill, lets the user review the resulting overview, and
5	then publishes it to a Confluence location that the user must specify. It is a
6	thin orchestrator: the overview work belongs to `han-coding:code-overview`, and the
7	publishing work belongs to `han-atlassian:markdown-to-confluence`. This skill only
8	validates its inputs, runs the overview to a scratch file, gets the user's review
9	and publish choice, and hands the file to the publisher.
10
11	`han-coding:code-overview` produces a single scratch file (the overview: what the
12	code does, how it flows, where to start, and — in PR mode — what changed and what
13	to watch when reviewing). It does not produce companion artifacts, so this skill
14	publishes that one file as a single Confluence page — the single-page sibling of
15	`han-atlassian:investigate-to-confluence` and `han-atlassian:project-documentation-to-confluence`,
16	not the parent-plus-children tree of `han-atlassian:plan-a-feature-to-confluence`.
17
18	The five steps below are the whole skill. It does not resolve Confluence pages or
19	call the Confluence MCP create/update tools itself; `han-atlassian:markdown-to-confluence`
20	owns all of that.
21
22	## Step 1: Validate Inputs
23
24	Confirm the skill has everything it needs before spending effort on an overview:
25
26	1. Atlassian MCP reachable (hard requirement). Call
27	`mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to confirm the
28	server is connected and retrieve the cloud ID(s). If the tool is not
29	available, the call errors, or it returns no accessible resources (typically
30	an authentication or configuration problem), stop immediately. Tell the
31	user this skill requires the Atlassian MCP server to be installed, configured,
32	and authenticated, and that they can re-run it once it is connected. Do not
33	fall back to a local-only run; for a local-only overview, point them at
34	`han-coding:code-overview`. This preflight runs first so a missing server fails
35	before any overview work begins.
36	2. A target to overview (optional). The target may be a file, directory,
37	symbol, or pull request reference, and an optional size (`small`, `medium`, or
38	`large`). All of this — together with the relevant conversation context — is
39	forwarded to `han-coding:code-overview` verbatim in Step 2. A target is not
40	required: with none given, `han-coding:code-overview` defaults to the current
41	branch's changes. Do not resolve or classify the target here; that is
42	`han-coding:code-overview`'s job.
43	3. A Confluence destination. Confirm the request provides a target location:
44	a Confluence page URL (to update that page, or create a child under it),
45	or a space (key or name) plus an optional parent page. If none was
46	provided, ask for one with `AskUserQuestion`, explaining plainly that the
47	skill needs an exact destination because it does not search Confluence. Do not
48	resolve the page tree here — only confirm a location was given. Carry it
49	through to Step 5; `han-atlassian:markdown-to-confluence` resolves it.
50
51	## Step 2: Produce the Overview to a Scratch File
52
53	Invoke the `han-coding:code-overview` skill with the Skill tool, **forwarding all
54	provided context** verbatim: the target (file, directory, symbol, or PR
55	reference, or none for the current branch's changes), any size the user gave, and
56	the relevant conversation context. Do not summarize, trim, or reinterpret the
57	user's context; pass it through so `han-coding:code-overview` runs exactly as it would
58	on its own (target resolution, mode and size selection, parallel
59	`codebase-explorer` exploration, synthesis, and the read

People who liked this also viewed

6 picks

Type

code-overview-to-confluence

122stars12forks

View on GitHub

How to install code-overview-to-confluence?

testdouble/han/code-overview-to-confluence

$npx -y skills add testdouble/han --skill code-overview-to-confluence

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Code Overview to Confluence
2
3	This skill runs a progressive-disclosure code overview with the core
4	`han-coding:code-overview` skill, lets the user review the resulting overview, and
5	then publishes it to a Confluence location that the user must specify. It is a
6	thin orchestrator: the overview work belongs to `han-coding:code-overview`, and the
7	publishing work belongs to `han-atlassian:markdown-to-confluence`. This skill only
8	validates its inputs, runs the overview to a scratch file, gets the user's review
9	and publish choice, and hands the file to the publisher.
10
11	`han-coding:code-overview` produces a single scratch file (the overview: what the
12	code does, how it flows, where to start, and — in PR mode — what changed and what
13	to watch when reviewing). It does not produce companion artifacts, so this skill
14	publishes that one file as a single Confluence page — the single-page sibling of
15	`han-atlassian:investigate-to-confluence` and `han-atlassian:project-documentation-to-confluence`,
16	not the parent-plus-children tree of `han-atlassian:plan-a-feature-to-confluence`.
17
18	The five steps below are the whole skill. It does not resolve Confluence pages or
19	call the Confluence MCP create/update tools itself; `han-atlassian:markdown-to-confluence`
20	owns all of that.
21
22	## Step 1: Validate Inputs
23
24	Confirm the skill has everything it needs before spending effort on an overview:
25
26	1. Atlassian MCP reachable (hard requirement). Call
27	`mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to confirm the
28	server is connected and retrieve the cloud ID(s). If the tool is not
29	available, the call errors, or it returns no accessible resources (typically
30	an authentication or configuration problem), stop immediately. Tell the
31	user this skill requires the Atlassian MCP server to be installed, configured,
32	and authenticated, and that they can re-run it once it is connected. Do not
33	fall back to a local-only run; for a local-only overview, point them at
34	`han-coding:code-overview`. This preflight runs first so a missing server fails
35	before any overview work begins.
36	2. A target to overview (optional). The target may be a file, directory,
37	symbol, or pull request reference, and an optional size (`small`, `medium`, or
38	`large`). All of this — together with the relevant conversation context — is
39	forwarded to `han-coding:code-overview` verbatim in Step 2. A target is not
40	required: with none given, `han-coding:code-overview` defaults to the current
41	branch's changes. Do not resolve or classify the target here; that is
42	`han-coding:code-overview`'s job.
43	3. A Confluence destination. Confirm the request provides a target location:
44	a Confluence page URL (to update that page, or create a child under it),
45	or a space (key or name) plus an optional parent page. If none was
46	provided, ask for one with `AskUserQuestion`, explaining plainly that the
47	skill needs an exact destination because it does not search Confluence. Do not
48	resolve the page tree here — only confirm a location was given. Carry it
49	through to Step 5; `han-atlassian:markdown-to-confluence` resolves it.
50
51	## Step 2: Produce the Overview to a Scratch File
52
53	Invoke the `han-coding:code-overview` skill with the Skill tool, **forwarding all
54	provided context** verbatim: the target (file, directory, symbol, or PR
55	reference, or none for the current branch's changes), any size the user gave, and
56	the relevant conversation context. Do not summarize, trim, or reinterpret the
57	user's context; pass it through so `han-coding:code-overview` runs exactly as it would
58	on its own (target resolution, mode and size selection, parallel
59	`codebase-explorer` exploration, synthesis, and the read

People who liked this also viewed

6 picks

Type