analyze-code
Run repository code analysis as a final check after completing prompts, targeting every changed Rust package by PackageNames.
소스 정보
- 저장소
- Azure/azure-sdk-for-rust
- 최근 소스 활동
- 2026년 9월 16일 22:53
- 감지된 SKILL.md 언어
- 영어
- 스타
- 886
- 포크
- 377
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- 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.
GitHub에서 보기