agentleFS
Sign inStart free
yasikyasik/agentlane/.agents/skills/code-change-verification/SKILL.md

code-change-verification

Skill9 starsChanged 12 days agoMITView on GitHub

Run the mandatory verification stack when changes affect runtime code, tests, or build/test behavior in the AgentLane repository.

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

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 3

    1. openai/openai-agents-python★ 31k15% same
    2. openai/openai-agents-js★ 4k12% same
    3. pproenca/unifi-mcp★ 232% same

    Wrote their own version · 3

    1. redis/ioredis★ 15ksame name
    2. openai/openai-guardrails-python★ 265same name
    3. openai/openai-guardrails-js★ 113same name

    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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 3

    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:

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

    line 10
  2. Distinctive:

    If any command fails, fix the issue, rerun the script, and report the failing output.

    line 15
  3. Very specific:

    If dependencies are not installed or have changed, run make sync first to install dev requirements via uv.

    line 20
  4. Very specific:

    Run from the repository root in this order: make format, make lint, make typecheck, make tests.

    line 21
  5. Distinctive:

    Do not skip steps; stop and fix issues immediately when a command fails.

    line 22

“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, tests, or build/test configuration. You can skip it for docs-only or repository metadata unless a user asks for the full stack.

Quick start

  1. macOS/Linux: bash .agents/skills/code-change-verification/scripts/run.sh.
  2. If any command fails, fix the issue, rerun the script, and report the failing output.
  3. Confirm completion only when all commands succeed with no remaining issues.

Manual workflow

  • If dependencies are not installed or have changed, run make sync first to install dev requirements via uv.
  • Run from the repository root in this order: make format, make lint, make typecheck, make tests.
  • Do not skip steps; stop and fix issues immediately when a command fails.
  • Re-run the full stack after applying fixes so the commands execute in the required order.

Resources

scripts/run.sh

  • Executes the full verification sequence with fail-fast semantics from the repository root. Prefer this entry point to ensure the required commands run in the correct order.

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