agentleFS
shim369shim369/Python-Smart-Health-Intelligence-Platform/.claude/skills/check/SKILL.md

check

Skill0 starsChanged 55 days agoMITView on GitHub

Run this project's full quality gate (ruff lint, ruff format, mypy, i18n duplicate-key check, unit tests against a safe dummy DB). Use after code changes and before committing, instead of running pytest directly — plain pytest can wipe the production Neon DB.

  • Reads credentials

88 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use daily-arxiv, exp-eval and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新

    Also in 5 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 5 projects that use this

  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • +6 more from Lambenthan
  • +1 more from skyllwt
  • Other versions88 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 88

    1. tw93/claude-health★ 7.6ksame name
    2. tw93/Waza★ 7.6ksame name
    3. tokio-rs/topcoat★ 7.2ksame name
    4. katanemo/archgw★ 7.1ksame name
    5. katanemo/plano★ 7.1ksame name
    6. Giskard-AI/giskard-oss★ 6ksame name
    7. VibiumDev/vibium★ 3ksame name
    8. skyllwt/OmegaWiki★ 1.7ksame name
    9. DAIR-AutoResearch/AutoSci★ 1.7ksame name
    10. PKU-DAIR/AutoSci★ 1.7ksame name

    78 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 75 edited versions we read keep these.

  • 1

    Distinctive

    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. Distinctive:

    Run the bundled script from the repository root:

    line 8
  2. Very specific:

    Never run pytest directly against the default environment.

    line 24
  3. Very specific:

    If ruff format fails, fix with .venv/bin/ruff format app src tests and re-run.

    line 25

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

/check

Run the bundled script from the repository root:

.claude/skills/check/check.sh

It runs, in order, and reports every failure (it does not stop at the first):

  1. ruff check app src tests
  2. ruff format --check app src tests
  3. mypy src
  4. Duplicate keys in TRANSLATIONS (app/i18n.py)
  5. pytest tests/unit with DATABASE_URL pointed at an unreachable localhost and tests/unit/test_migrations.py excluded

Rules

  • Never run pytest directly against the default environment. Without .env.test, tests/unit/test_migrations.py drops and recreates every table in the .env production DB, and tests/integration/ writes to it. A PreToolUse hook (.claude/hooks/guard_pytest_db.py) blocks such runs.
  • If ruff format fails, fix with .venv/bin/ruff format app src tests and re-run.
  • Report the final ALL PASSED / FAILED: ... line to the user; on failure include the failing step's output.

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.