How do I install the Post Work Review skill?

Run npx skillmds@latest add tomevault-io/post-work-review in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Post Work Review safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Post Work Review?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Post Work Review free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Post Work Review?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Post Work Review by tomevault-io — Agent Skill

Name: Post Work Review
Author: tomevault-io

File contents

Post-Work Review

Review your diff against AGENTS.md rules and fix violations before presenting work.

Process

Run git diff HEAD (or appropriate base) to see all changes
Read AGENTS.md fully -- the rules section is authoritative
For each changed file, check every rule that applies
Fix violations directly -- do not just report them
Re-run type check (npx tsc --noEmit or go build ./...)

High-Signal Checks

These are the violations most commonly introduced under time pressure:

Check	Rule	How to spot
Type casts	AVOID `as` statements	grep for `as` in diff
Any types	AVOID `any` type	grep for `: any` or `as any`
Let bindings	AVOID `let` statements	grep for `let` in diff
Else branches	DO NOT use `else` unless necessary	grep for `} else`
Dead code	Delete unused code when changing things	check if old code is still referenced
String interpolation	Use `cn()` not template literals for className	grep for className={`
Obvious comments	DO NOT use obvious comments	read comments -- are they saying what the code already says?
Disabled linters	DO NOT disable linter warnings unless necessary	grep for `eslint-disable` in new lines

Quick Grep

# Run against staged/unstaged changes
git diff HEAD -U0 | grep -E '^\+.*\bas\b' | grep -v '^+++' | grep -v 'import.*as'
git diff HEAD -U0 | grep -E '^\+.*: any' | grep -v '^+++'
git diff HEAD -U0 | grep -E '^\+.*\blet\b ' | grep -v '^+++'
git diff HEAD -U0 | grep -E '^\+.*\} else' | grep -v '^+++'
git diff HEAD -U0 | grep -E '^\+.*eslint-disable' | grep -v '^+++'

Common Misses

Casts introduced to satisfy a generic -- rethink the generic or type parameter instead
undefined as void -- undefined is assignable to void directly
let for a variable reassigned once -- restructure to use const
Dead imports -- after deleting code, check if its imports are still needed
Comments describing the obvious -- // Release all resources above releaseAllResources() adds nothing

Source: s4wave/spacewave — distributed by TomeVault.

---name: post-work-reviewdescription: Use after completing implementation work to catch AGENTS.md violations, dead code, and issues missed during development. Run before showing results to the user. Use when this capability is needed.---# Post-Work ReviewReview your diff against AGENTS.md rules and fix violations before presenting work.## Process1. Run `git diff HEAD` (or appropriate base) to see all changes2. Read `AGENTS.md` fully -- the rules section is authoritative3. For each changed file, check every rule that applies4. Fix violations directly -- do not just report them5. Re-run type check (`npx tsc --noEmit` or `go build ./...`)## High-Signal ChecksThese are the violations most commonly introduced under time pressure:| Check | Rule | How to spot ||-------|------|-------------|| Type casts | AVOID `as` statements | grep for ` as ` in diff || Any types | AVOID `any` type | grep for `: any` or `as any` || Let bindings | AVOID `let` statements | grep for `let ` in diff || Else branches | DO NOT use `else` unless necessary | grep for `} else` || Dead code | Delete unused code when changing things | check if old code is still referenced || String interpolation | Use `cn()` not template literals for className | grep for `` className={` `` || Obvious comments | DO NOT use obvious comments | read comments -- are they saying what the code already says? || Disabled linters | DO NOT disable linter warnings unless necessary | grep for `eslint-disable` in new lines |## Quick Grep```bash# Run against staged/unstaged changesgit diff HEAD -U0 | grep -E '^\+.*\bas\b' | grep -v '^+++' | grep -v 'import.*as'git diff HEAD -U0 | grep -E '^\+.*: any' | grep -v '^+++'git diff HEAD -U0 | grep -E '^\+.*\blet\b ' | grep -v '^+++'git diff HEAD -U0 | grep -E '^\+.*\} else' | grep -v '^+++'git diff HEAD -U0 | grep -E '^\+.*eslint-disable' | grep -v '^+++'```## Common Misses- **Casts introduced to satisfy a generic** -- rethink the generic or type parameter instead- **`undefined as void`** -- `undefined` is assignable to `void` directly- **`let` for a variable reassigned once** -- restructure to use `const`- **Dead imports** -- after deleting code, check if its imports are still needed- **Comments describing the obvious** -- `// Release all resources` above `releaseAllResources()` adds nothing---> Source: [s4wave/spacewave](https://github.com/s4wave/spacewave) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Post Work Review