← ClaudeAtlas

conferlisted

Publish HTML docs to your team's Confer for review, and retrieve approved team docs as context. Use when asked to "push/publish to confer", "open a doc review", or when authoritative team context is needed (architecture, conventions, runbooks) — query Confer MCP before guessing.
rohansx/confer · ★ 2 · AI & Automation · score 65
Install: claude install-skill rohansx/confer
# Confer GitHub PRs for docs. **Agents write, humans approve, agents read only what's approved, with provenance.** ## When to use - The user asks you to "publish a doc to Confer" or "push to Confer". - The user asks you to "open a doc for review" (then run `confer open`). - You need authoritative team context (architecture, conventions, runbooks, postmortems) before making a code change ��� **query Confer MCP first**. ## How to publish (confer push) 1. **Generate self-contained single-file HTML** — inline CSS, no external fetches. The viewer applies a strict CSP (`default-src 'none'; script-src 'unsafe-inline'; style-src 'unsafe-inline'; img-src data:;`), so anything you link to or fetch from outside will be blocked. Test the HTML in a browser with the same CSP before pushing. 2. **Auto-detected provenance** — `confer push` automatically grabs `git remote get-url origin`, `git rev-parse HEAD`, and the current branch. You don't need to pass them. 3. **Run**: ``` confer push path/to/doc.html --space <s> --slug <slug> ``` - `--space`: the team area (e.g. `backend`, `frontend`). - `--slug`: the doc's stable identifier inside that space. Lowercase, dash-separated. - `--draft` if not ready for human review yet. 4. **The CLI prints a review URL** — share that with the team. A human owner must approve before the version becomes part of the corpus. 5. **Never attempt to approve.** Approval is human-only and API-enforced. The CLI ha