Markdown compatibility2 detected · 0 enabled · 0 missing assets · mkdocs docs · 2 warnings
- HomeREADME.md
- Getting starteddocs/getting-started.md
- Core conceptsdocs/core-concepts.md
- Demo walkthroughdocs/demo-walkthrough.md
- Review pull requestsdocs/review-pull-requests.md
- Review repository branchesdocs/review-repository-branches.md
- Draft reviewsdocs/draft-reviews.md
- Brainstorming Reviewsdocs/brainstorming-reviews.md
- Live Preview Reviewsdocs/web-app-reviews.md
- Commentary Formsdocs/commentary-forms.md
- Review progressdocs/review-progress.md
- Review modesdocs/review-modes.md
- Workspacedocs/workspace.md
- Markdown renderingdocs/markdown-rendering.md
- Markdown extensionsdocs/markdown-extensions.md
- Static HTML reviewdocs/static-html-review.md
- Knowledge BrainCurrent page
- Access and authenticationdocs/access-and-authentication.md
- Developer accessdocs/developer-access.md
- Generate a GitHub PATdocs/generate-a-github-pat.md
- Azure DevOpsdocs/azure-devops.md
- Commentary CLIdocs/commentary-cli.md
- Agent skillsdocs/agent-skills.md
- API and MCPdocs/api-and-mcp.md
- API referencedocs/api/reference.md
- MCP toolsdocs/api/mcp-tools.md
- Blogdocs/blog.md
- Troubleshooting and FAQdocs/troubleshooting-and-faq.md
- MkDocsMkDocs is a Pro Markdown feature that is not enabled for this viewer. MkDocs-specific syntax remains visible as ordinary Markdown when compatibility rendering is unavailable.
- Repository link validationPro can validate links across this repo. Links still render with standard repository-aware rewriting.
Knowledge Brain
Knowledge Brain mode is for reviewing AI-maintained knowledge bases before they are merged or published.
When To Use It
Use Knowledge Brain review when a branch updates source notes, generated wiki pages, project memory, research claims, LLM outputs, Open Knowledge Format bundles, or other knowledge-base files. Commentary keeps the work in the normal rendered document review shell, but adds brain-aware navigation and review context.
Common patterns include:
- LLM wikis with raw source notes, wiki pages, and generated briefs
- research brains with papers, concepts, claims, citations, and evaluation ledgers
- project brains with architecture notes, ADRs, incidents, and runbooks
- agent-maintained support or product knowledge bases
- OKF bundles with concepts, index files, logs, and bundle-root concept links
Brain Workspace
When Knowledge Brain mode is active, the file navigator groups files by role instead of showing only a flat Markdown list. Typical groups include sources, wiki pages, outputs, and other control or support files.
Open Knowledge Format profiles add OKF-oriented concept, index, and log navigation groups, bundle-root absolute concept links, and OKF conformance health findings.
Brain review can add:
- review summaries for changed knowledge
- wikilinks and backlinks between pages
- source-to-wiki comparison context
- health findings for broken links, missing source trails, duplicate entities, risky content, OKF conformance, and schema issues
- provenance views for claims and their source references
- knowledge-diff and graph-review context for relationship changes
- evaluations for manual golden-question checks
Some advanced Brain surfaces are Pro preview features. They remain usable during the preview period and show the standard Pro notice when opened. The OKF review profile itself is a free feature.
Public Readers
Published public Brain readers expose a read-only document view for public repositories or public snapshots.
Reader pages keep repository ownership visible and link back to the original source. App-native review comments and private review data are not rendered in public reader pages.
Private Brain publishing is a Pro preview feature and requires sign-in before private content is rendered.
API And Agent Workflows
API and MCP clients can inspect Knowledge Brain review state with scoped tokens. Supported workflows include listing Brain reviews, changed Brain files, review comments, health findings, requested revisions, ready-for-review replies, and evaluation ledgers.
Use public commentary-dev fixture repositories for demos and read-only validation. Mutating automation belongs only in dedicated test fixture repositories.