agentleFS
Sign inStart free
EmeaAppGbbEmeaAppGbb/spec2cloud/.github/skills/build-check/SKILL.md

build-check

Skill100 starsChanged 7 months agoMITView on GitHub

Verify that all project services (API and Web) build successfully. Check compilation errors, type errors, and lint warnings. Use before running tests, before deployment, after code changes, and on resume. Trigger when build verification, compilation check, or pre-test validation is needed.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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:

    Verify builds succeed before proceeding with tests or deployment.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Build Check

Verify builds succeed before proceeding with tests or deployment.

Build Commands

ServiceSource BuildDocker Build
API (TypeScript)cd src/api && npm run builddocker build -f src/api/Dockerfile .
Web (Next.js)cd src/web && npm run builddocker build -f src/web/Dockerfile .

Steps

  1. Identify services — Read azure.yaml or scan src/ for service directories
  2. Build each service — Run the source build command for each service
  3. Capture errors — Collect compilation errors, type errors, and warnings
  4. Docker build (if preparing for deployment) — Run Docker build for each Dockerfile
  5. Report — Summarize build status per service

Output Format

Service: <name>
Status: PASS | FAIL
Errors: <count>
Warnings: <count>

Details:
- <file>:<line> <error message>

Notes

  • Web (Next.js) requires output: 'standalone' in next.config.ts
  • API uses TypeScript with Express

Mandatory Completion Checklist

The orchestrator MUST verify ALL of the following before marking build-check as complete:

  • Every service (API, Web) has been built — none skipped
  • Each service reports PASS or FAIL with error/warning counts
  • If any service fails to build, the failure details (file, line, message) are included
  • A partial build (one service passes, another not attempted) is reported as "incomplete" — not as PASS

BLOCKING: A build-check with any FAIL or incomplete service means the codebase is not ready for testing or deployment. The orchestrator must fix build errors before proceeding.

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.

Check your setup, free