Skip to main content

analyze-code

Run repository code analysis as a final check after completing prompts, targeting every changed Rust package by PackageNames.

Source facts

Repository
Azure/azure-sdk-for-rust
Last source activity
September 16, 2026 at 22:53
Detected SKILL.md language
English
Stars
886
Forks
370

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
analyze-code
description
Run repository code analysis as a final check after completing prompts, targeting every changed Rust package by PackageNames.
# Analyze changed packages Run this as a final check after completing any prompt that changes repository files. 1. Collect changed files from Git, including staged, unstaged, untracked, and deleted files: ```bash { git diff --staged --name-only; git diff --name-only; git ls-files --others --exclude-standard -- 'sdk'; } | sort -u ``` 2. Assume service crates live under `sdk/<service-directory>/<crate-name>`. For each changed file under `sdk/`, derive the candidate crate directory from the first three path segments and keep it only when `<crate-directory>/Cargo.toml` exists. Include any crate names specified in the prompt, then collect and deduplicate all `<crate-name>` values as package names. 3. Run the analyzer once from the repository root with all changed package names: ```powershell ./eng/scripts/Analyze-Code.ps1 -PackageNames @('<crate-name-1>', '<crate-name-2>') ``` If neither changed files nor the prompt identify a service crate, report that no packages need analysis. Otherwise, report the packages analyzed and any failures.
View on GitHub