review

Analyze Rust code in the k23 repository for safety violations and correctness issues.

649|43|Updated Oct 12, 2023
One-click install
npx skills add https://github.com/JonasKruckenberg/k23 --skill review-jonaskruckenberg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/JonasKruckenberg/k23/tree/main/.claude/skills/review
Command: npx skills add https://github.com/JonasKruckenberg/k23 --skill review-jonaskruckenberg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the need for efficient, thorough code reviews tailored to the specific nuances of the k23 microkernel project, reducing manual effort and catching issues early.

Core Features & Use Cases

  • Targeted Code Analysis: Checks for unsafe patterns, unsafe Rust code, and unsafe assembly in the repository.
  • Citations & Evidence: Ensures each finding is supported by a spec, RFC, or source file location.
  • Real-World Use: Automate review of pull requests or branches to identify safety violations, potential bugs, and adherence to standards before human review.

Quick Start

Run the review on the current branch with jj diff and analyze the output for issues related to unsafe code or safety violations.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate Rust code review for unsafe patterns and safety violations?

Automate Rust code review by analyzing the current branch with `jj diff` to identify unsafe patterns, unsafe assembly, and correctness issues, reducing manual effort and catching safety violations early before human review.

What is static analysis for unsafe Rust code in a microkernel repository?

Static analysis for unsafe Rust code identifies safety violations, unsafe patterns, and correctness issues within the repository context, emphasizing high-confidence findings to ensure code quality and adherence to best practices during rapid review cycles.

How do I get citations for code review findings on unsafe Rust blocks?

Get citations for code review findings by ensuring each identified safety violation is supported by a spec, RFC, or source file location, providing verifiable evidence for every detected unsafe pattern or correctness issue during analysis.

Does this static analysis tool work with general Rust projects or only specific repositories?

This static analysis tool works specifically with the k23 microkernel repository, tailoring code evaluation to the project's unique nuances by targeting unsafe Rust code and unsafe assembly within this defined context for high-confidence findings.

What's the best way to identify safety violations in Rust assembly code before human review?

The best way to identify safety violations is to run automated targeted code analysis on your current branch, checking for unsafe Rust code and unsafe assembly to catch high-confidence findings early and streamline the human review process.

When should I use automated preflight code review for Rust safety violations?

Use automated preflight code review when you need to evaluate pull requests or branches for safety violations and potential bugs before human review, designed for rapid review cycles to ensure adherence to repository standards early.