Skip to content
Back to skills

Tmb Swe Checklist

ASecurity

SWE's self-review heuristics — load only when about to atomic-close. Mechanical patterns (bare except, missing timeout, mutable defaults, etc.) are caught by the plugin's code-quality-lint hook; this skill carries the spec-fidelity and scope discipline judgment.

  • 6 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 21, 2026
ai-agents

Security analysis

A100/100

Scanned October 21, 2026

npx -y skills add trustmybot/plugin --skill tmb_swe-checklist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tmb Swe Checklist?

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

Security grade badge for Tmb Swe Checklist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/trustmybot-tmb-swe-checklist/badge)](https://www.skillsdirectory.com/skills/trustmybot-tmb-swe-checklist)

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: tmb_swe-checklist
description: SWE's self-review heuristics — load only when about to atomic-close. Mechanical patterns (bare except, missing timeout, mutable defaults, etc.) are caught by the plugin's code-quality-lint hook; this skill carries the spec-fidelity and scope discipline judgment.
---

# SWE Self-Review

Before `task_update_status(completed)`, confirm these by reading the diff. Mechanical patterns (bare except, mutable defaults, etc.) are caught by the plugin's `code-quality-lint` hook on every Edit/Write. You check the things only a human reader would see.

- **Spec fidelity.** Every bullet under `## Success Criteria` and every error/edge case named in `## Description` has a concrete change in the diff. Quote the item, point to the diff line.
- **Scope discipline.** Your close report lists every path you edited outside the typed `files[]`, each with the reason it had to change. No "while I was there" cleanups. No new TODOs.
- **Tests for what you touched.** Run the tests and lints covering the files you changed and paste their pass/fail with the tail of their output. The gate runs `verification[]` once when you close and records the run for your commit. A dry run or smoke test reports as its command's pass/fail.
- **Changelog.** Where the repo records changes per PR (a fragment directory or a CHANGELOG section), add the task's entry the way the repo does and leave any generated changelog file to its generator.
- **Hook blocks.** A PreToolUse block is a hard stop — surface its exact output and wait.

Escalate (not guess) when:

- The spec contradicts itself — quote the contradiction.
- A required fact is missing from the spec — quote what's missing.
- 3 attempts at the same approach failed — show what you tried.

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.