القائمة
Work with Confluence over its REST API (no MCP) — read/search (CQL), summarize pages, find docs, create/update/comment/label. Use for any read/search/create/update on Confluence pages, or references to a remembered space, page, or doc.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | confluence |
| description | Work with Confluence over its REST API (no MCP) — read/search (CQL), summarize pages, find docs, create/update/comment/label. Use for any read/search/create/update on Confluence pages, or references to a remembered space, page, or doc. |
Read ../../references/codex-adapter.md, then read ../../../skills/confluence/SKILL.md and follow the source skill through that Codex adapter. Keep the source skill's gates and rules.
Codex equivalents:
<plugin-root>/bin/confluence for whoami|get <id> [body]|search "<CQL>"|raw <METHOD> <path> [json]. It wraps the REST API; don't hand-write curl, and never use an ambient Confluence/Atlassian MCP even if one appears in the tool list — use the CLI.CONFLUENCE_BASE_URL + a token (CONFLUENCE_API_TOKEN/CONFLUENCE_PAT/CONFLUENCE_PROD_PAT) from the environment. On missing config, use ../../../skills/confluence/setup.md only as API guidance: explain how to provide variables to the current Codex environment or shell. Do not edit Claude settings, Codex global config, or secret files; never type/echo the secret.<magician-state>/confluence-memory.md; create it only after an authorized write.Systematic performance profiling and optimization with a mandatory baseline-first gate — measure before changing, re-measure after. Use when something is slow or you need to hit a latency/throughput target.
Blameless post-mortem / RCA — gathers facts, reconstructs a timeline, runs 5-Whys, defines action items, writes the post-mortem file and commits it. Use after an incident or outage.
Structured design dialogue with a visual companion — produces an approved spec and design artifacts before any implementation begins. Use at the start of a feature, before writing code.
Thorough, research-grounded code review of a change, PR, or MR — multi-lens (correctness, security, simplification, tests), severity-ranked with impact + fix, configurable depth, optional PR comments. Use when asked to review code, "do a code review", "review this PR/MR", "review my changes/diff/branch", or audit a changeset before merge.
Use when the user asks to research, investigate, analyze, find out, explore, examine, audit, or evaluate something — structured multi-source research with consulting, library-doc search, web search, and guided output delivery.
Multi-agent code review AND remediation — dispatches correctness, security, and simplification reviewers in parallel, consolidates findings, then fixes criticals/highs. Use when reviewing a diff or PR before shipping.