Use Commentary to review plans before coding and Markdown-heavy pull requests before merge, without replacing GitHub as the source of truth.
Run both commands in GitHub Copilot CLI. The first adds the public skills repository; the second installs the review plugin.
copilot plugin marketplace add commentary-dev/commentary-skills
copilot plugin install commentary-review@commentary-skillsSource and setup details are maintained in commentary-dev/commentary-skills. This is a repository marketplace integration, not a vendor marketplace listing.
The artifact, feedback, revision, and approval state stay explicit from start to finish.
Start from an explicit artifact and named owner.
Keep the current state and unresolved context visible.
Keep the current state and unresolved context visible.
Keep the current state and unresolved context visible.
The next stage begins only after verification.
Plan review catches wrong assumptions early. Rendered pull-request review catches document quality and reader-impact problems after the source exists. Commentary supports both without changing GitHub ownership.
Repository access stays tied to provider permissions. App-native threads remain the durable review record, while provider comments are synchronized representations around it.
Use the next page that matches the artifact or boundary you need to review.
Review Copilot-generated plans, Markdown pull requests, and documentation as readable artifacts, then return structured feedback through skills, plugins, Git, API, or MCP.