Menu
Re-check a prior assistant claim. Use when user says "nack", "not convinced", or "check again"; not for review feedback.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | nack |
| description | Re-check a prior assistant claim. Use when user says "nack", "not convinced", or "check again"; not for review feedback. |
Negative acknowledgement: treat the user's pushback as a request to re-check, not as hostility or approval.
Inspect only what bears on the challenged point:
git status --short --branch before edits;codebase-map-understand.md only for cross-module or architecture claims, then verify named files in live source.Evaluate external reviewer feedback against live code and tests before applying it. Use grill-me or grill-with-docs for full plan stress tests.
Rechecking: <specific claim>.Changed: original claim was wrong or too strong; correct it.Stands: original claim still holds; cite the evidence briefly.Blocked: the evidence needed is unavailable; ask one focused question or name the command/approval needed.Before editing, confirm ownership, blast radius, validation signal, and whether the correction changes prior user intent.
A useful NACK pass includes the challenged claim, evidence checked, verdict, and any validation for changes made.
Do not treat pushback as approval to broaden scope, rewrite history, deploy, spend money, expose secrets, or make destructive changes. Do not argue from confidence; use evidence.
Rechecking: <claim/action>
Verdict: Changed|Stands|Blocked — <one-line reason>
Evidence: <files/commands/context checked>
Next: <small safe action or question>
User: nack, not convinced. check again
Agent: re-checks the latest recommendation against the repo, then either corrects it or says why it still stands with evidence.
Follow the shared skill contract for repo study, dirty-worktree hygiene, verification evidence, safe handoffs, and safety defaults.
Resolve short approval against the latest checkpoint. Use for "lgtm", "looks good", "approved", or "go ahead"; not risky or review feedback.
UI/UX routing front door. Use as the front door for broad or ambiguous UI/UX work that needs the right build, redesign, audit, design-system, accessibility, or browser specialist. Do not use when the user already names a narrower UI skill.
Proposes UI Vault resource upgrades for a selected webpage. Use when the user asks for libraries, assets, effects, or inspiration for an existing page. Do not use for implementation or greenfield design.
Upload, list, or delete files with s3upload and return expiring Azure links. Use for configured temporary Azure storage; not for S3 or cloud setup.
Ship local Git changes by inspecting, polishing, validating, split-committing, and pushing. Use for commit, push, ship, delivery audit, or delivery blockers; not deploys or releases.
Remove proven unreachable code in small validated batches. Use when asked to find and delete dead, stale, orphaned, or unused code; not for dependency pruning, over-engineering reports, or speculative cleanup.