agentleFS
tapiotorstitapiotorsti/torsti-tapiola-website/.agents/skills/verify-changes/SKILL.md

verify-changes

Skill0 starsChanged 3 days agoMITView on GitHub

Run the checks that must pass before finishing or committing any code change in this repo (lint, type check, tests, production build) and review the diff for project-rule violations. Use before every commit or before reporting a task as done.

  • Reads credentials

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use intelligent-routing, design-spec 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.
  • SKB3002Skill

    intelligent-routing

    Automatic agent selection and intelligent task routing. Analyzes user requests and automatically selects the best specialist agent(s) without requiring explicit user mentions.

    Also in 3 projects that use this

  • jornalistainclusivoSkill

    design-spec

    How to author a DESIGN.md file — the machine-readable design-token + human-rationale format that must exist before any UI is built. YAML front-matter token schema (colors, typography, spacing, rounded, components), type system, token references, and canonical section order.

    Also in 3 projects that use this

  • xenitV1Skill

    bash-linux

    Bash/Linux terminal patterns. Critical commands, piping, error handling, scripting. Use when working on macOS or Linux systems.

    Also in 3 projects that use this

  • xenitV1Skill

    red-team-tactics

    Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.

    Also in 3 projects that use this

  • xfstudioSkill

    rust-pro

    Master Rust 1.75+ with modern async patterns, advanced type system

    Also in 3 projects that use this

  • +7 more from xenitV1

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    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 four checks and keep going after a failure, so you see every problem at once:

    line 13
  2. Distinctive:

    If a check already failed before your change, say so in your report instead of fixing unrelated code.

    line 31
  3. Distinctive:

    Run git diff and check:

    line 39

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

Verify changes

The main branch syncs to Lovable and deploys from there, so every commit must leave the site in a working state.

1. Run the checks

Run all four checks and keep going after a failure, so you see every problem at once:

bun run lint
bunx tsc --noEmit
bun run test
bun run build
  • Fix the errors your change introduced. Do not silence a rule with eslint-disable or @ts-ignore unless you explain the reason in a comment.
  • Known lint baseline: much of the existing code (generated by Lovable) is not Prettier-formatted, so bun run lint already reports many prettier/prettier errors on main. Do not reformat the whole repo as part of an unrelated task. Instead, lint only the files you changed, for example bunx eslint src/routes/things.tsx, and make those files clean. On Windows with core.autocrlf=true, ignore Delete ␍ errors: they come from the checkout, not from the committed files.
  • If a check already failed before your change, say so in your report instead of fixing unrelated code.
  • src/routeTree.gen.ts is regenerated by the dev server or the build. If you added or removed a route, run the build so the file updates, and commit the regenerated file.

2. Review the diff

Run git diff and check:

  • No edits to generated files (routeTree.gen.ts excepted when regenerated, src/integrations/supabase/types.ts, src/components/ui/*, drizzle/meta/*).
  • No content hard-coded into components; content belongs in the database.
  • No secrets, service-role keys or new .env values.
  • New public routes have a complete head(): title, description, og tags.
  • Database changes come as a new migration file with RLS. Old migrations are unchanged.
  • No leftover console.log or debug code.

3. Report

State which checks passed, which failed and why, and anything you could not verify, for example a migration that only Lovable Cloud can apply.

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.