← all publishers

SteveVitali

@stevevitali source repo

Report this profile Claim this profile

• 11 skills
• 0 followers
• 16 hours ago last updated

1. ▌
   Review Pr · stevevitali bundle

   Review someone else's GitHub PR as a Staff Engineer and post a high-precision review — mechanical grounding (CI, local verification), focused design + security passes, calibrated severity labels, inline comments with suggestion blocks. Use when asked to review a PR, give feedback on a PR, or act as a code reviewer.
   0
   installs
2. ▌
   Agent Docs · stevevitali bundle

   Create or converge agent documentation (AGENTS.md hierarchy) for a codebase — bootstrap mode generates docs from scratch, refresh mode detects and fixes drift
   0
   installs
3. ▌
   Self Review · stevevitali bundle

   Two-pass self-review of the current branch: mechanical verification (build/test/lint + checklists) then a Staff Engineer design critique
   0
   installs
4. ▌
   Build Memory · stevevitali bundle

   Owns the build-memory contract that the multi-session build skills share: the committed layout under docs/build/, docs/tickets/ and docs/adr/, the templates, the validator, and legacy-scratch migration. Use it to initialise the layout in a repo (init), validate it (check), migrate a legacy gitignored scratch dir into the committed tree (migrate), or regenerate the ADR index (adr-index). Other skills cite skills/build-memory/layout.md rather than restating the layout.
   0
   installs
5. ▌
   Decompose Spec · stevevitali bundle

   Turn one large spec into an optimally-partitioned, dependency-ordered ticket plan — the fewest self-contained tickets that each fit one fresh-context implementation run — and seed a durable build ledger plus per-ticket contract files and a manifest runbook (relocatable into the repo tree via tickets_dir). The planning half of a multi-session build; pairs with orchestrate-build.
   0
   installs
6. ▌
   Implement Spec · stevevitali bundle

   Spec-driven, autonomous end-to-end: branch → plan + test matrix → implement (tests alongside) → self-review → gap-analysis vs spec → close gaps → rigorous downstream verification → PR + evidence report
   0
   installs
7. ▌
   Reconcile Build · stevevitali bundle

   The closeout procedures the tail REC.* tickets invoke — backlog + operational readiness, spec reconciliation, and the integration plan — for a multi-session build. Use it when a build's tickets have landed and the tail rows (from decompose-spec) call 'invoke reconcile-build mode=…', the way P22.x tickets called refresh-repo-docs. Reads the committed build memory (DEFERRALS, ADRs, OPEN FINDINGS, the coverage matrix, BUILD_INDEX) and writes the backlog / reconciliation / integration artifacts. Not a sequencer and not a merge tool.
   0
   installs
8. ▌
   Synthesize Spec · stevevitali bundle

   Turn a brief into a ratified, decomposable spec the way orchestrate-build turns a plan into a build: a durable research ledger whose rows are executed in fresh contexts, then synthesis, adversarial review, and operator ratification. Use it for the UPSTREAM half of a large build — when the spec does not yet exist or is still a moving target and the work spans research, design, and operator decisions across multiple sessions. Pairs with decompose-spec (it writes the decomposition-prompt.md hand-off). For a spec that already exists, skip this and run decompose-spec.
   0
   installs
9. ▌
   Orchestrate Build · stevevitali bundle

   Drive a decomposed spec to completion across fresh contexts: SETUP a dedicated worktree, run each ticket end-to-end through implement-spec in a fresh context, update the durable ledger, report progress, pause for intervention at ticket boundaries, and finish with a whole-build capstone verification. The execution half of a multi-session build; pairs with decompose-spec.
   0
   installs
10. ▌
    Refresh Repo Docs · stevevitali bundle

    Audit and sync a repo's human-facing documentation (README, docs/, CHANGELOG, CONTRIBUTING, examples) against the actual code — detect drift deterministically, fix stale claims, remove cruft, fill gaps, and verify every claim written. Use when docs are outdated, after major feature work, or on a periodic docs-hygiene pass.
    0
    installs
11. ▌
    Address Pr Comments · stevevitali bundle

    Work through unresolved review comments on your PR as the author: triage every thread, implement fixes where the reviewer is right, push back with rationale where they aren't, answer questions, commit + push, and reply to every thread with what happened. Use when asked to address, respond to, or resolve PR review feedback.
    0
    installs