analyze-code
Run repository code analysis as a final check after completing prompts, targeting every changed Rust package by PackageNames.
Datos de origen
- Repositorio
- Azure/azure-sdk-for-rust
- Última actividad en el origen
- 16 de septiembre de 2026 a las 22:53
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 885
- Forks
- 375
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- 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.
Ver en GitHub