agentleFS
nwiizonwiizo/claudelytics/.claude/skills/dev-setup/SKILL.md

dev-setup

Skill88 starsChanged 8 months agoMITView on GitHub

Development environment setup - Rust toolchain, cross-compilation targets, dependencies, git hooks, IDE config.

  • Installs packages

8 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

1 rule. 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Create .git/hooks/pre-commit with format check, clippy, and test gates.

    line 41

“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

Development Environment Setup

Setup focus: $ARGUMENTS

Step 1: Rust Toolchain

rustup update stable
rustup default stable
rustup component add rustfmt clippy
cargo install cargo-watch cargo-edit cargo-outdated cargo-audit cargo-tarpaulin

Step 2: Cross-Compilation Targets

rustup target add x86_64-unknown-linux-gnu
rustup target add x86_64-unknown-linux-musl
rustup target add x86_64-pc-windows-msvc
rustup target add x86_64-apple-darwin
rustup target add aarch64-apple-darwin

Step 3: Dependencies

cargo update
cargo outdated
cargo audit

Step 4: Git Hooks

Create .git/hooks/pre-commit with format check, clippy, and test gates. Make executable with chmod +x.

Step 5: Development Tools

cargo install tokei ripgrep cargo-expand cargo-criterion

Step 6: Environment Variables

export RUST_BACKTRACE=1
export RUST_LOG=claudelytics=debug

Quick Commands

TaskCommand
Watch testscargo watch -x test
Debug runRUST_LOG=debug cargo run -- daily
Benchmarkcargo bench --bench parser_bench
Docscargo doc --no-deps --open
Macro expandcargo expand models

Verification

cargo fmt --check && cargo clippy -- -D warnings && cargo test && cargo build --release

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.