agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azure-sdk-for-rust/.github/skills/analyze-code/SKILL.md

analyze-code

Skill887 starsChanged 29 days agoMITView on GitHub

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

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this as a final check after completing any prompt that changes repository files.

    line 8
  2. Distinctive:

    Run the analyzer once from the repository root with all changed package names:

    line 21
  3. Distinctive:

    If neither changed files nor the prompt identify a service crate, report that no packages need analysis.

    line 27

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

    { 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:

    ./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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free