Claude Skills by hamza-ali-shahjahan

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

The cleanup stage. When a build hits a milestone (pre-launch, end of a sprint, "let's tidy this up"), scan a repo — or 100+ repos at once — for rot, see the extent at a glance, then clean it with confirmation. Report-first, never silently edits. Works on any git repo, Hamzaish-built or not.

Find and fix prose in a repo that only makes sense from inside the session that wrote it — dead references to a conversation, change narration ("used to", "no longer"), reviewer-addressed asides, and pointers to work that never landed. Use before a PR, before publishing docs, and when a repo has been written largely by agents. The test is one question - could a reader at HEAD, with no transcript, verify every claim?

Run a full validation pass on an idea — sharpening, devil's advocate, market sizing, competitor mapping, customer discovery plan.

Turn a rough ambition into a measurable, REACHABLE goal — a capability statement, a precisely-named metric, ≥2 numeric evals, an acceptance rule, and non-goals — with a feasibility check that catches impossible or game-able targets before you chase them. Pair with /goal (which pursues a goal autonomously).