AutoSkillit
CLAUDE.md5 starsChanged 6 months agoMITView on GitHub
Rules for maintaining .github/workflows/ files. Enforced for both human and AI contributors. The correct input parameter for pinning the uv version is version, not uv-version. uv-version is an output of the action (the resolved installed version), not an input. Jobs that do not run uv sync MUST disable setup-uv caching to avoid poisoning the wheel cache consumed by downstream jobs: Jobs that run uv sync --locked may omit enable-cache (defaults to auto, enabled on GitHub-hosted runners). dtolnay/rust-toolchain is only needed…
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- tests/CLAUDE.mdCLAUDE.md
- audit-archSkill
- audit-bugsSkill
- audit-cohesionSkill
- audit-defense-standardsSkill
- audit-testsSkill
- chart-courseSkill
- check-bearingSkill
- design-guardsSkill
- elaborate-phaseSkill
- id-slopSkill
- make-arch-diagSkill
- make-reqSkill
- make-scenariosSkill
- promote-to-mainSkill
- render-recipeSkill
- review-promotionSkill
- update-architectureSkill
- update-reqsSkill
- update-specsSkill
- validate-auditSkill
- verify-diagSkill
The file
Files
CI Workflow Constraints
Rules for maintaining .github/workflows/ files. Enforced for both human and AI contributors.
setup-uv parameter names
The correct input parameter for pinning the uv version is version, not uv-version.
# CORRECT
- uses: astral-sh/setup-uv@v7
with:
version: "0.9.21"
# WRONG — silently ignored, installs latest uv instead of pinned version
- uses: astral-sh/setup-uv@v7
with:
uv-version: "0.9.21"uv-version is an output of the action (the resolved installed version), not an input.
Caching discipline
Jobs that do not run uv sync MUST disable setup-uv caching to avoid poisoning the
wheel cache consumed by downstream jobs:
- uses: astral-sh/setup-uv@v7
with:
version: "0.9.21"
enable-cache: false # required for jobs that skip uv syncJobs that run uv sync --locked may omit enable-cache (defaults to auto, enabled on
GitHub-hosted runners).
Rust toolchain scope
dtolnay/rust-toolchain is only needed in jobs that compile native Python extensions
(i.e., jobs that run uv sync). Do not add it to preflight, lint, or other utility jobs
that only run uv lock --check or similar commands.
Lockfile verification
The preflight job exists to validate the lockfile early and cheaply. It must NOT install
the full dependency tree — only uv lock --check. Adding uv sync to preflight defeats
the purpose of the job separation.
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
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.

