publish

What problem does it solve? Finished markdown documents — plans, audits, reviews, retros, decisions, knowledge pages — often die in scratch directories because routing them to the right destination (a shared vault, a repo's documentation tree, a GitHub issue, a PR description, or Notion) is manual and inconsistent. This Skill acts as the single output sink: it validates house-style frontmatter and body skeletons, deduplicates per medium, and routes one manuscript to whichever destination the caller requests. ## Core Features & Use Cases - Multi-destination adapters: Publish the same markdown source to a shared-docs vault (with Claudron engine detection and raw-tree fallback), a repo's documentation/ tree, a GitHub issue, a PR description, the chat session, or a Notion page. - Deep validation before publishing: Enforces frontmatter schema (title, type, status, owner, created) and per-type body skeletons, including a hard gate on the Implementation Plan section that downstream build automation depends on. - Bounded GitHub dedup: Runs three deliberately varied lexical searches against open issues, checks counts against query limits to avoid false negatives, and supports in-place issue body updates via --update. - Use Case: After an audit skill produces a findings document with valid frontmatter, run publish with --to github-issue --repo myrepo to dedup against existing issues, create the issue with labels mapped from tags, and write the issue URL back into the doc's links: field. ## Quick Start Publish the finished audit document findings.md as a GitHub issue in the current repository, running dedup checks first.