confluence-explain-doc
Write and publish a Confluence page (or Jira/report text) that explains a bug's cause, logic, and fix so a first-time reader understands it. Code-capture first: real source lines with red/green/blue line highlights and line-numbered captions, one section per problem, how problems connect, git blame plus the original reason for each cause, details folded. Use for "write this up in Confluence", "explain the root cause", "I don't understand this explanation", "progressive disclosure", 컨플 정리, 설명 문서, 원인 설명.
Original · translation is not supported for this source languageTarget: Software development & testing. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- confluence-explain-doc
- 0. Load the domain profile first
- 1. Page structure (fixed order)
- 2. Code captures
- 3. Cause rows: blame plus original background
- 4. Noise removal (before every publish)
- 5. Publish and check
- Writing
Goal: a reader who opens the page once can explain the problem to someone else. Real code carries the explanation; prose stays minimal. Company/project specifics (site, space, branch names, glossary, label language, token location) live outside this skill so the skill stays portable. Read the first one that exists: 1. the file in $EXPLAINDOCDOMAIN 2. /.explain-doc/domain.md 3. /docs/agents/explain-doc-domain.md No profile: ask for the Confluence site, space key, and the "before" ref (usually the production branch). Template: references/domain-profile.md. No format headings ("Summary", "Overview", "TL;DR", "Click to expand"). Headings name the content. 1. Opening paragraph (no heading, 2-3 sentences): how many problems, the shared object they touch (one table, one value), and how they differ (e.g. one writes the wrong value, the other reads it and sends it). 2. One section per problem, numbered in the priority the user sets ( Problem N. : ). When you renumber, fix every "Problem N" reference too. Four lines ( , keyword — one plain sentence): symptom → cause → evidence it really happened or original background (with blame) → fix (commits). Define each term the first time it appears;
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- cskwork/skills
- Source file
- skills/productivity/confluence-explain-doc/SKILL.md
- Fixed revision
- 3cbcf7c00b169da79fee5e91699440729b0eb84b
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: cskwork/skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-12T03:01:42.951Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.