Skip to content
Back to skills

Self Verify

ASecurity

Run typecheck, lint, and tests on changed files as the last step before declaring a task complete - don't let the user be the one who discovers a broken build. Use before reporting any code change as finished.

  • 66 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 24, 2026
ai-agents

Security analysis

A100/100

Scanned September 24, 2026

npx -y skills add smnatale/dotfiles --skill self-verify --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Self Verify?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Self Verify
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/smnatale-self-verify/badge)](https://www.skillsdirectory.com/skills/smnatale-self-verify)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: self-verify
description: Run typecheck, lint, and tests on changed files as the last step before declaring a task complete - don't let the user be the one who discovers a broken build. Use before reporting any code change as finished.
disable-model-invocation: false
---

# Self-verify

Before saying a task is complete, run the project's typecheck, lint, and any relevant tests against the files you changed. This is the last step of the task, not an optional follow-up.

Catching a broken build is your job. If typecheck, lint, or a test fails because of your own change, fix it before reporting done - don't hand back a "done" that regresses to a failure the user then has to find and report back.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.