twg-confluence

twg

CLI launcher fallback

twg <command>

command not found

$HOME/.local/bin/twg

$env:LOCALAPPDATA\Programs\twg\bin\twg.exe

Use When

• Use for Confluence-anchored content or space reads and mutations, including CQL, bodies, hierarchy, versions, permissions, and exports.
• Do not load for a supporting Confluence link in a broader workflow.

First Route

confluence content get

confluence search query --cql

lastmodified

content list

confluence content

confluence space

confluence tree

twg help describe "<exact path>"

Confluence Semantics

• Use the unified content surface for content operations advertised by live help; use

  confluence space

  for spaces and

  confluence tree

  for hierarchy.
• Search snippets are discovery candidates. Read the selected content before summarizing or editing it.
• Page titles are supplied separately from bodies. Do not repeat the title as the first body heading.
• Remix create commands create an asset, not a page embed. For a visual on the page, continue with the HTML guide already loaded, update that page, and read it back; an asset ID or URL alone is not completion proof.

Safe Authoring And Editing

• Treat user authorization and CLI confirmation as separate checks for archive, trash, and purge. The CLI requirement to pass

  --yes

  is an execution preflight, not evidence that the user authorized the mutation. Use

  --yes

  only after the user explicitly named the mutation and the exact target or a previously displayed bounded target set.
• Explicit instructions such as "archive page XYZ" or "archive those 15 pages" after a concrete list authorize execution without another confirmation. Vague outcome language such as "clean up", "organize", "remove clutter", or "take care of" does not authorize archive, trash, or purge.
• If the mutation or targets were inferred, read and resolve the proposed targets, present the exact action and bounded target list, and wait for the user to affirm that mutation. Do not generalize approval from a similar prior action.

  trash

  does not authorize an additional permanent purge.
• Before authoring, read and apply the target space's instructions by key or ID; see

  references/spaces.md

  . Empty instructions mean use defaults.
• Prefer

  live_doc

  for collaborative or co-authored internal content when the target supports it. Bare "page" or "doc" creation also defaults to live docs.
• Use

  page

  for explicit classic/non-live intent, knowledge bases, customer help, established classic-page spaces, or page-only operations. Preserve an existing target's type; a classic parent or reference does not set a new child's type.
• For non-trivial edits, read current content, save the body locally, edit the file, then update with the snapshot token.
• Use the lossless HTML round trip when macros or exact storage representation matter.
• Use

  --dry-run

  only for explicit preview or validation requests, or for unusually risky edits where direct execution was not requested.
• Read back the content or space after mutation and report its URL.

Handoffs

• Load

  twg-context-discovery

  for related Jira work, projects, goals, or dependencies; load

  twg-responsibility-routing

  for people, ownership, authority, or escalation.
• Load

  twg-status-rollups

  when pages contribute to a broader status report.
• Load

  twg-operational-health

  for runbooks, incidents, PIRs, or reliability evidence.

References

• references/content.md

  - content types, reads, writes, and exports

• references/editing.md

  - concurrency-safe body editing

• references/spaces.md

  - space lifecycle and hierarchy

• references/querying.md

  - CQL and fuzzy discovery

• references/body-formats.md

  - HTML, markdown, mentions, and special formats