agentleFS
pproencapproenca/unifi-mcp/.agents/skills/code-change-verification/SKILL.md

code-change-verification

Skill2 starsChanged 7 months agoMITView on GitHub

Run the verification stack (format, lint, typecheck, test) when changes affect runtime code, tests, or build config.

6 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Ensure work is only marked complete after formatting, linting, type checking, and tests pass.

    line 10
  2. Distinctive:

    Run from the repository root:

    line 22
  3. Distinctive:

    Stop and fix issues immediately when a command fails.

    line 26

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

Code Change Verification

Overview

Ensure work is only marked complete after formatting, linting, type checking, and tests pass. Use this skill when changes affect runtime code (src/), tests, or build configuration. Skip it for docs-only or repository metadata changes unless a user asks for the full stack.

Quick start

bash .agents/skills/code-change-verification/scripts/run.sh

The script runs npm run format first, then npm run lint, npm run typecheck, and npm test in parallel with fail-fast semantics.

Manual workflow

Run from the repository root:

  1. npm run format — apply formatting fixes
  2. Then in parallel: npm run lint, npm run typecheck, npm test
  3. Stop and fix issues immediately when a command fails.
  4. Re-run the full stack after applying fixes.

When to run

  • Changes to src/ (server code, tools, types)
  • Changes to tests/
  • Changes to package.json, tsconfig.json, or CI config

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.