codekb-review

Review and confirm AI-extracted knowledge entries via CodeKB CLI or MCP tool.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill codekb-review-te-quanbzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codekb-review
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/codekb/skills/codekb-review
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill codekb-review-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-extracted knowledge entries are provisional until a human verifies them, and low-confidence or stale entries can pollute a codebase knowledge base. This Skill provides a structured review workflow to confirm, reject, or edit knowledge entries so the knowledge base stays accurate. ## Core Features & Use Cases - Entry Review Workflow: Confirm accurate entries (confidence raised to 1.0), reject inaccurate ones, or edit content in place via codekb review CLI commands or the codekb_review MCP tool. - Lifecycle Management: Track entry statuses including accepted, draft, potentially_stale, superseded, and rejected, with filtering via codekb list flags. - Git-Tracked Audit Trail: Every modification is captured in Git history under codekb/knowledge/, enabling full traceability of review decisions. - Use Case: After codekb extract reports low-confidence entries, list entries with potentially_stale status, verify each against the actual source code, then confirm or reject them before they are used in an OpenSpec proposal workflow. ## Quick Start Ask the AI to list all potentially stale CodeKB knowledge entries and review each one against the source code, confirming accurate entries and rejecting inaccurate ones.

Frequently Asked Questions about codekb-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review low-confidence knowledge entries in CodeKB?

Run codekb list --status potentially_stale to find entries needing review, verify each against the actual source code, then use codekb review <id> confirm, reject, or edit. Confirming an entry raises its confidence to 1.0.

What happens when I confirm or reject a CodeKB knowledge entry?

Confirming sets the entry confidence to 1.0 and marks it accepted so it appears in default retrieval. Rejecting marks it as rejected, excluding it from search results while keeping it in Git history.

Can I review CodeKB entries through an MCP tool instead of the CLI?

Yes, the codekb_review MCP tool accepts an id, a verdict of confirm, reject, or edit, and an optional edit string. It performs the same review operations as the codekb review CLI command.

Are rejected or superseded CodeKB entries permanently deleted?

No, rejected entries remain in Git history and superseded entries stay accessible via codekb list --include-superseded. All modifications are tracked in Git under the codekb/knowledge/ directory.

When should I review knowledge entries before using them?

Review entries with confidence below 0.7 before relying on them in workflows like /opsx:propose. AI-extracted knowledge is provisional until a human confirms it, so periodic audits are recommended.