Axum Code Review

v1.0.0

Reviews axum web framework code for routing patterns, extractor usage, middleware, state management, and error handling. Use when reviewing Rust code that us...

0· 60·0 current·0 all-time
byKevin Anderson@anderskev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the content: the skill only instructs the agent to inspect Cargo.toml, source routing/extractor/middleware patterns, state, and error handling — all expected for an axum code-review helper.
Instruction Scope
SKILL.md confines runtime behavior to reading project files (Cargo.toml, source files) and applying review rules; it does not instruct network exfiltration, reading unrelated system files, or accessing environment secrets. The only external-looking item is the line 'Load and follow beagle-rust:review-verification-protocol' — this is a procedural reference (no URL or install step) and should be clarified before use.
Install Mechanism
No install spec and no code files to execute; instruction-only skills carry minimal install risk.
Credentials
The skill requests no environment variables, credentials, or config paths — nothing disproportionate to a static code-review helper.
Persistence & Privilege
Defaults for persistence/privileges are used (always: false, autonomous invocation allowed). The skill does not request permanent presence or system-wide changes.
Assessment
This skill is an instruction-only axum code-review checklist and appears internally consistent. Before installing: (1) confirm what 'beagle-rust:review-verification-protocol' refers to and where it lives (it could be an external process or internal doc you may need to trust); (2) be aware the agent will need read access to the repository being reviewed—don't grant access to private repos or credentials you don't want inspected; (3) because the skill can be invoked autonomously by agents (platform default), restrict agent permissions appropriately so it can't access unrelated systems or secrets. If you need to be extra cautious, run reviews in an isolated environment or with a read-only checkout of the codebase.

Like a lobster shell, security has layers — review code before you run it.

latestvk974mbgq5adqbr6hv916k5p5fd83pj3y

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments