agentleFS
nwiizonwiizo/claudelytics/.claude/skills/qa-pipeline/SKILL.md

qa-pipeline

Skill88 starsChanged 8 months agoMITView on GitHub

Comprehensive quality assurance - tests, linting, formatting, code analysis, and release build verification.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Check for outdated dependencies: cargo outdated

    line 15
  2. Very specific:

    Update dependencies if needed: cargo update

    line 31
  3. Distinctive:

    Verify public APIs have documentation

    line 42
  4. Distinctive:

    Check for missing examples in doc comments

    line 43
  5. Distinctive:

    Update CHANGELOG.md if needed

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Quality Assurance Pipeline

QA focus: $ARGUMENTS

Step 1: Project Analysis

  • Analyze codebase structure and dependencies
  • Check for outdated dependencies: cargo outdated
  • Verify module organization

Step 2: Quality Checks (parallel)

cargo test --verbose
cargo fmt --check
cargo clippy -- -D warnings

Step 3: Issue Resolution (based on findings)

  • Fix formatting issues: cargo fmt
  • Fix clippy warnings: apply suggested fixes
  • Debug and correct failing tests
  • Update dependencies if needed: cargo update

Step 4: Final Verification

cargo test --release
cargo build --release

Step 5: Documentation Check

  • Verify public APIs have documentation
  • Check for missing examples in doc comments
  • Update CHANGELOG.md if needed

Checklist

  • All tests pass
  • No clippy warnings
  • Code properly formatted
  • Release build succeeds
  • Documentation complete

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.