How do I install the Project Checks skill?

Run npx skillmds@latest add maroffo/project-checks in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Project Checks safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Project Checks?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Project Checks free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Project Checks?

maroffo (@maroffo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Project Checks by maroffo — Agent Skill

Name: Project Checks
Rating: 4.666666666666667 (3 reviews)
Author: maroffo

Project Checks

Scaffold a Makefile with language-specific check targets (lint, vet, fmt, vuln, test). Auto-detects project languages from marker files. Use when user says project checks, scaffold checks, add make check, or /project-checks. Not for running checks (the advanced-review preflight does that).

maroffo Updated Sep 10, 2026

File contents

ABOUTME: Scaffold Makefile with language-specific check targets

ABOUTME: Auto-detect, generate, ask before modifying existing Makefiles

Project Checks (Makefile Scaffolding)

Generates a Makefile with a check target that runs lint, vet, format checks, vulnerability scanning, and tests specific to the project's language(s). The result is committed to the repo and used by CI, pre-commit hooks, and the advanced-review preflight gate.

Trigger

Activate when the user says: "project checks", "scaffold checks", "add make check", or /project-checks.

Execution Flow

Step 1 - Detect languages

Scan the project root for marker files:

Marker	Language
`go.mod`	Go
`pyproject.toml` or `setup.py`	Python
`package.json`	JavaScript/TypeScript
`Gemfile`	Ruby
`Cargo.toml`	Rust

Multiple languages can be detected (e.g., Go backend + Python scripts).

Step 2 - Generate Makefile

Load the template for each detected language from templates/<lang>.mk. Combine into a single Makefile with:

check target that depends on all language-specific sub-targets
Sub-targets: lint, vet, fmt-check, vuln, test
Each sub-target runs the appropriate tool for the language

Step 3 - Handle existing Makefile

If a Makefile already exists:

Show the diff (what targets would be added)
Ask the user before modifying
Merge new targets without touching existing ones

If no Makefile exists: generate it directly.

Step 4 - Report

Show what was generated and suggest next steps:

make check to run all checks
Add to CI pipeline
The advanced-review preflight will auto-detect and use it

Language Templates

Each template defines the standard tooling for that language. Templates are in templates/<lang>.mk and use Make variables for tool paths so users can override them.

Advisory targets (Go)

templates/go.mk also ships two targets that are deliberately outside check, run by hand when a review needs a number instead of an argument:

Target	Tool	Purpose
`crap`	crap4go	CC, coverage and CRAP per function, from the standard coverage profile. Evidence for a finding, not a gate: no threshold (see `rules/quality-gates.md`, Finding Contract)
`mutation`	gremlins	`make mutation PKG=./internal/foo`. Surviving mutants are evidence of tautological tests. Slow (recompiles and reruns the suite per mutant), so never in `check` or the inner loop

Both install their tool on demand via go install when it is missing.

When to Use

New project that needs a standardized check target
Existing project without a unified lint/test/vuln command
After the advanced-review preflight says "no make check target found"

When NOT to Use

Project already has a working make check or equivalent
CI-only checks that don't make sense locally

---name: project-checksdescription: Scaffold a Makefile with language-specific check targets (lint, vet, fmt, vuln, test). Auto-detects project languages from marker files. Use when user says project checks, scaffold checks, add make check, or /project-checks. Not for running checks (the advanced-review preflight does that).---# ABOUTME: Scaffold Makefile with language-specific check targets# ABOUTME: Auto-detect, generate, ask before modifying existing Makefiles# Project Checks (Makefile Scaffolding)Generates a `Makefile` with a `check` target that runs lint, vet, formatchecks, vulnerability scanning, and tests specific to the project'slanguage(s). The result is committed to the repo and used by CI, pre-commithooks, and the advanced-review preflight gate.## TriggerActivate when the user says: "project checks", "scaffold checks","add make check", or `/project-checks`.## Execution Flow### Step 1 - Detect languagesScan the project root for marker files:| Marker | Language ||--------|----------|| `go.mod` | Go || `pyproject.toml` or `setup.py` | Python || `package.json` | JavaScript/TypeScript || `Gemfile` | Ruby || `Cargo.toml` | Rust |Multiple languages can be detected (e.g., Go backend + Python scripts).### Step 2 - Generate MakefileLoad the template for each detected language from `templates/<lang>.mk`.Combine into a single Makefile with:- `check` target that depends on all language-specific sub-targets- Sub-targets: `lint`, `vet`, `fmt-check`, `vuln`, `test`- Each sub-target runs the appropriate tool for the language### Step 3 - Handle existing MakefileIf a `Makefile` already exists:1. Show the diff (what targets would be added)2. Ask the user before modifying3. Merge new targets without touching existing onesIf no `Makefile` exists: generate it directly.### Step 4 - ReportShow what was generated and suggest next steps:- `make check` to run all checks- Add to CI pipeline- The advanced-review preflight will auto-detect and use it## Language TemplatesEach template defines the standard tooling for that language. Templates arein `templates/<lang>.mk` and use Make variables for tool paths so users canoverride them.### Advisory targets (Go)`templates/go.mk` also ships two targets that are deliberately **outside**`check`, run by hand when a review needs a number instead of an argument:| Target | Tool | Purpose ||--------|------|---------|| `crap` | crap4go | CC, coverage and CRAP per function, from the standard coverage profile. Evidence for a finding, not a gate: no threshold (see `rules/quality-gates.md`, Finding Contract) || `mutation` | gremlins | `make mutation PKG=./internal/foo`. Surviving mutants are evidence of tautological tests. Slow (recompiles and reruns the suite per mutant), so never in `check` or the inner loop |Both install their tool on demand via `go install` when it is missing.## When to Use- New project that needs a standardized check target- Existing project without a unified lint/test/vuln command- After the advanced-review preflight says "no make check target found"## When NOT to Use- Project already has a working `make check` or equivalent- CI-only checks that don't make sense locally

Frequently asked questions