agentleFS
rikeda71rikeda71/cxbridge/.claude/skills/run-checks/SKILL.md

run-checks

Skill1 starsChanged 6 months agoMITView on GitHub

Runs fmt, clippy, and tests after modifying the Rust implementation, or before committing. Use when asked to "run checks", "cargo check", "run checks", or "make CI pass".

6 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, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If this fails, run cargo fmt and then re-verify.

    line 20
  2. Very specific:

    If this fails, fix each clippy finding.

    line 28
  3. Very specific:

    When suppressing with #[allow(...)], always include a reason comment.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 6 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

Steps

Execute the following in order. If a step fails, fix the issue before proceeding to the next step.

1. Format check

cargo fmt --check

If this fails, run cargo fmt and then re-verify.

2. Clippy (warnings as errors)

cargo clippy -- -D warnings

If this fails, fix each clippy finding. When suppressing with #[allow(...)], always include a reason comment.

3. Tests

cargo test

Fix any failing tests. If snapshots (insta) were updated, run cargo insta review to inspect the diff before accepting.

Completion condition

Report completion once all 3 steps pass with exit code 0.

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.