workreview
Work Review Skill
Produces a reviewer-facing report that summarizes all work done in a given commit range. The report content uses a single unified template regardless of whether the skill is invoked from specmgr finalize or standalone — the only things that differ are the output filename and the default scope.
workreview does NOT track implementation details itself. It consumes the #### Implementation Log sections that specmgr writes into spec files and chunk plans during implementation, and consolidates them into the report.
Two invocation modes
Both modes use the same report template. They differ only in output filename and default scope.
Mode A — spec-finalize (called from specmgr)
Invoked from specmgr Workflow 3 (single-pass) or Workflow 4 (chunked) at the finalize step of a DRAFT → IMPLEMENTED transition.
- Output file:
specs/done-reports/{spec-basename}-review.md - Example:
specs/claim-domain-spec.md→specs/done-reports/claim-domain-spec-review.md - Scope: the commits implementing the spec (typically
main..HEADof the implementation branch)
More from gclayburg/agent-skills
specmgr
>
22buildgit
Jenkins CI/CD build pipeline monitor. Check build status, push and monitor builds, follow builds in real-time, and analyze build timing, executor capacity, pipeline structure, and queue contention. Use when the user asks about CI/CD status, build results, wants to push code and monitor the Jenkins build, asks if CI is passing, or needs help optimizing Jenkins throughput. Triggers include "check build", "build status", "is CI passing", "is the build green", "push and watch", "push and monitor", "what failed in CI", "why did the build fail", "follow the build", "watch the build", "trigger a build", "run the build", "why is Jenkins slow", "which agents are busy", "what is in the queue", "show pipeline structure", and "find the bottleneck".
18