Victor Rentea

You can implement tickets with self-review via /implement-ticket, assemble tabbed human-review reports with diagram deltas and REST contract diffs via /human-review, and publish demo snapshots or report screenshots to GitHub Pages via /publish-demo and /human-review-publish-demo.

These skills target developers and reviewers who need structured change-set auditing. They suit engineers implementing tickets who must document fixes, declined items and assumptions, plus reviewers consuming tabbed reports with Code City shots, feature videos and endpoint-complexity increments.

All four skills use explicit invocation only: type /implement-ticket <ticket>, /human-review, /publish-demo, or /human-review-publish-demo. Model invocation is disabled, so each command runs only when the user types it, committing and pushing results to the repository.

The /human-review skill requires a committed review-points.md produced by the coding agent during /implement-ticket, listing what was fixed, declined and assumed. It then assembles review.html with diagram deltas, a Code City shot, feature video and deep-linked snippets.

The /publish-demo skill copies a finished human-review page into the repo's demo/ folder, renders its landing-page card, commits and pushes, producing the GitHub Pages copy, a rolling zip and the ghcr image. /human-review-publish-demo pushes per-tab screenshots in light and dark modes.