PR

project-review

Performs a full audit of firmware projects to ensure documentation and config match the code.

Install

mkdir -p .claude/skills/project-review && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17386" && unzip -o skill.zip -d .claude/skills/project-review && rm skill.zip

Installs to .claude/skills/project-review

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Comprehensive, whole-project coherence review of the tesla-key-esp32 firmware — finds bugs, inconsistencies, doc/code drift, config/build mismatches, and cross-cutting incoherence so docs, code, config and the build all agree and the project is correct. Use whenever the user asks to "review the project", "project review", audit the repo, "check docs/code for errors/inconsistencies", check that everything is consistent/coherent, or after a batch of changes to make sure nothing drifted. Reach for this even when they don't say "review" — any "is the whole thing still right/coherent?" request fits.
601 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • Audit project-wide coherence
  • Verify documentation and code synchronization
  • Check build configurations and partition tables
  • Validate runtime invariants

How it works

The agent compares documentation claims against actual code, build configurations, and runtime invariants to identify drift and inconsistencies.

Inputs & outputs

You give it
Project review request
You get back
Coherence audit report

When to use project-review

  • Review firmware project consistency
  • Check documentation and code drift
  • Verify config and build synchronization

About project-review

Reviews project-wide coherence, including build configurations, documentation drift, and runtime invariants. It checks that code, docs, and build settings are synchronized.

Comprehensive, whole-project coherence review of the tesla-key-esp32 firmware — finds bugs, inconsistencies, doc/code drift, config/build mismatches, and cross-cutting incoherence so docs, code, config and the build all agree and the project is correct. Use whenever the user asks to "review the proj

Prerequisites

ESP-IDF 5.x environment

Limitations

  • Cannot fix library bugs directly in managed components
  • Requires local ELF file for accurate crash backtrace decoding

How it compares

It performs a holistic cross-cutting audit of the entire project structure instead of checking individual files for style.

Compared to similar skills

project-review side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
project-review (this skill)01moReviewAdvanced
deepwiki-rs2510moReviewIntermediate
python-code-style97moReviewIntermediate
code-review-excellence196moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

deepwiki-rs

sopaco

AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.

25170

python-code-style

wshobson

Python code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.

971

code-review-excellence

wshobson

Master effective code review practices to provide constructive feedback, catch bugs early, and foster knowledge sharing while maintaining team morale. Use when reviewing pull requests, establishing review standards, or mentoring developers.

1958

code-walk-thru

pchalasani

Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.

670

cookbook-audit

anthropics

Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.

568

schema-markup

davila7

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," or "breadcrumb schema." For broader SEO issues, see seo-audit.

1042

Search skills

Search the agent skills registry