deep-review

Review the manifold-csg workspace for Rust idioms, FFI safety, and test gaps.

19|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/zmerlynn/manifold-csg --skill deep-review-zmerlynn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-review
Source: https://github.com/zmerlynn/manifold-csg/tree/main/.claude/skills/deep-review
Command: npx skills add https://github.com/zmerlynn/manifold-csg --skill deep-review-zmerlynn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Thoroughly audits the manifold-csg workspace to identify defects, safety concerns, and improvement opportunities across crates.

Core Features & Use Cases

  • Systematic Rust idioms review, FFI safety checks, API consistency, and test coverage assessment.
  • Identify dead code, performance hotspots, and ergonomic improvements for maintainability.
  • Use Case: a maintainer requests a full code audit before a major release across all crates.

Quick Start

Inspect the manifold-csg workspace and report findings across all crates.

Frequently Asked Questions about deep-review

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

FAQPage Schema
How do I perform a thorough code review for Rust crates in a workspace?

A thorough code review for Rust crates audits all source files, dependencies, and API surfaces to surface idiomatic Rust issues, FFI risks, code smells, and test gaps. It systematically compares code against quality criteria to produce prioritized remediation recommendations.

What does an FFI safety check cover during a static analysis of Rust code?

An FFI safety check during static analysis identifies risks at foreign function interfaces in Rust code. It reviews unsafe blocks and boundary definitions across crates to prevent memory violations and ensure robust cross-language interoperability.

How do I identify code smells and dead code in a Rust workspace before a release?

Identifying code smells and dead code in a Rust workspace involves systematically inspecting all source files to detect unused structures and ergonomic issues. This static analysis highlights maintainability improvements and performance hotspots.

Can I assess test coverage and API consistency across multiple Rust crates?

Yes, you can assess test coverage and API consistency across multiple Rust crates by applying a comprehensive review criteria. This evaluates test gaps and checks API surfaces to ensure uniform design and reliability across the workspace.

What is the best way to generate prioritized remediation recommendations for Rust code?

The best way to generate prioritized remediation recommendations for Rust code is through a deep end-to-end audit that scores findings by severity. This file-scoped approach targets defects and improvement opportunities directly.

Why does my Rust static analysis report code smells and test gaps across my workspace?

Static analysis reports code smells and test gaps because it systematically evaluates the workspace against comprehensive criteria for idiomatic Rust and documentation. It surfaces these issues to highlight maintainability risks and missing test coverage.