Nicholas Sollazzo

Systematic requirements discovery through focused multi-round questioning before any code gets written — asking only what the code can't reveal.

Drive a GitHub PR to a fresh approval, green CI, and a mergeable state — verifying every review finding against the code, fixing the real ones, and pushing back with evidence on the rest.

Green tests are not a running app — build the production image, boot it against a fresh throwaway database, probe the real routes and contracts, fix, and re-boot until everything answers.

Write the success criteria and load-bearing assumptions first, complete exactly one step per pass while restating done / verified / left, and loop until every criterion is checked off and backed by evidence.

Align new code to the codebase's own idioms — sample its neighbors, fix one mismatch per pass, and when two patterns conflict pick the more recent or better-tested one rather than averaging them.

Collapse a menu of options into one committed recommendation — research each candidate with real evidence instead of priors, score against explicit criteria, and don't stop until a single pick stands with a named runner-up.

Treat every operational claim in your docs and runbooks as a hypothesis — verify each against the live system, fix what drifted, and loop until no claim fails verification.

Extract a shared unit only where the same logic appears three or more times — and inline back any abstraction used only once or twice.

Unofficial CLI for the Fatture in Cloud API v2 — JSON-first, jq-pipeable, agent-friendly.

Audit a doc, PR description, or answer for unsourced assertions and replace each hedge with a cited artifact — file:line, command output, or URL — until nothing rests on inference.

Mutate your own production code on purpose, prove a test fails for each change, and loop until no surviving mutant slips past the suite.

Before a large batch job, surface the few decisions only the owner can make, lock them in one up-front interview, then run the whole batch unattended — looping on blockers, not on questions.

After merging, loop until production actually reflects the merge — pipeline green, the new commit serving, fresh routes answering, and schema plus data applied.

Before editing a symbol, map every caller, re-export, test, and shared util it touches — iterate until the blast radius is fully known, then write.

Attack your own just-built feature's trust assumptions — spoofable identifiers, client-settable fields, lookalike handles, reclamation attacks — fix each break and re-attack until every attack fails.

Distill a coding session's hard-won lessons — gotchas, patterns, integration quirks — into the project's knowledge base, with explicit approval before anything is written.

After every schema edit, regenerate migrations and prove there is no drift — loop until a fresh generate produces no new files and leaves the working tree clean.

After significant work, distill the non-obvious lessons — gotchas, environment quirks, corrections you received — into durable notes, looping until a fresh review pass surfaces nothing unrecorded.

Take a finished change from working tree to a green, mergeable PR — one command chaining simplify, verify, code-review, smart-commit, branch hygiene, PR, and babysit-to-green.

A Claude Code plugin that takes a finished change from working tree to a green, mergeable PR, then drives the review loop to a fresh approval.

Hunt down swallowed errors, empty catch blocks, ignored return codes, silent fallbacks, and skipped tests, then make each one fail loud or carry an explicit comment justifying the suppression.

Cluster uncommitted changes into logical groups and commit each with a clean conventional commit message — plus a Keep-a-Changelog update pass.

When your sync pipeline only upserts, removals never propagate — loop until the live store's rows exactly match the curated source files, pruning orphans deliberately.

Shrink an over-broad diff back to the minimum that satisfies the goal — every changed line load-bearing, no drive-by edits — re-running tests after each cut.

For every candidate item in a catalog or dataset, independently re-verify the claim and mechanically confirm its source URL resolves — include it with evidence or drop it with a written reason.

Run lint, typecheck, tests, and build as one chained gauntlet under a 'a warning FAILS' bar, and loop until the whole chain exits clean with the word 'warning' nowhere in its output.

Agentic coding tool that lives in your terminal, understands your codebase, and executes routine tasks, explains code, and handles git workflows via natural language.

The official Docker command-line interface for building, running, and managing containers, images, networks, and volumes against the Docker daemon.

Docker CLI plugin to define and run multi-container applications from a single declarative YAML file with one command.

GitHub's official command-line tool for working with pull requests, issues, releases, and the GitHub API from the terminal.