cc-update-review

Classify Feature Table additions and block PRs lacking implementation proposals.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/lane2077/claude-code-harness-zh --skill cc-update-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cc-update-review
Source: https://github.com/lane2077/claude-code-harness-zh/tree/main/skills/cc-update-review
Command: npx skills add https://github.com/lane2077/claude-code-harness-zh --skill cc-update-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates governance during Claude Code CC updates by detecting doc-only additions to the Feature Table and requiring explicit implementation proposals to prevent incomplete work from advancing.

Core Features & Use Cases

  • Classifies new Feature Table entries into three categories (A: existing implementations, B: documentation-only with no implementation, C: CC automatic inheritance) and validates that changes exist for A entries across hooks/scripts/agents/skills/core; flags B entries to block PRs without implementation plans.
  • Provides a structured internal review flow for CC integration PRs, including a checklist and guardrails to ensure changes are actionable and traceable.

Quick Start

Trigger the CC update review on a PR that touches the Feature Table to enforce accompanying implementation proposals.

Frequently Asked Questions about cc-update-review

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

FAQPage Schema
How do I block PRs that add Feature Table entries without implementation?▼

You can block doc-only PRs by triggering a CC update review that detects new Feature Table additions without corresponding implementation changes and enforces explicit proposals before advancing.

What is a doc-only Feature Table addition in a Claude Code integration PR?▼

A doc-only Feature Table addition is a new entry in docs/CLAUDE-feature-table.md that lacks corresponding changes in hooks, scripts, agents, skills, or core, which the review classifies as a category B entry to block.

How does the Feature Table entry classification work during a PR review?▼

The classification sorts new entries into category A for existing implementations, B for documentation-only additions lacking implementation, and C for CC automatic inheritance, validating that A entries have matching code changes.

Can I use this guardrail for PRs that only modify CLAUDE.md?▼

Yes, the guardrail applies to Claude Code CC integration PRs that modify either CLAUDE.md or docs/CLAUDE-feature-table.md, ensuring any Feature Table changes include actionable implementation proposals.

What are the limitations of automating governance for CC update reviews?▼

This guardrail is limited to Claude Code CC integration PRs touching CLAUDE.md or the Feature Table, and it cannot enforce implementation proposals for changes outside these specified files.