agentleFS
cykedevcykedev/vereinsheim/.claude/skills/check/SKILL.md

check

Skill1 starsChanged 14 days agoApache-2.0View on GitHub

Run all 5 monorepo quality gates (lint, format:check, test, tsc, next build) across the affected apps and report which are green/red. Use before every commit, or when the user asks to check/verify/confirm the build is clean.

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

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run all gates from the repo root — turbo-cached, over all apps and packages:

    line 6

“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

Run all gates from the repo root — turbo-cached, over all apps and packages:

pnpm check

Per app this runs: lint (eslint src), format:check (prettier), test (vitest), check-types (tsc --noEmit, in apps after that app's build, which regenerates the .next/types that tsc reads), build (next build); the Go bridge apps/spiegel-bridge maps the same tasks to go vet, gofmt, go test, go build. next build is mandatory — it catches build-only errors (e.g. the Next rule that a "use server" file may only export directly-declared async functions) that lint/tsc/test do not see.

The test gate needs the shared dev Postgres up (Ringwerk and Spiegel have DB-integration tests):

docker compose -f docker-compose.dev.yml up -d

Scope to one app: pnpm check --filter ringwerk (or spiegel, spiegel-bridge).

Report concisely: which gates are green, which are red, and — if red — the relevant error message(s). Suggest concrete fixes when the cause is clear.

Dev-Server vorher stoppen. Das Gate (next build) und ein laufender next dev teilen sich apps/<app>/.next; der Build zerlegt dabei .next/types/validator.ts und check-types wird rot, obwohl der Diff sauber ist (TS2307 './routes.js'). Nach einem abgebrochenen Build erst .next räumen — bei gestopptem Server, sonst verliert der Dev-Server sein .next/dev und antwortet bis zum Neustart mit Cannot read properties of undefined (reading 'call'). Siehe vault/incidents/next-dist-dir-shared-with-dev-server.md.

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.