tjboudreaux/cc-engineering-skills · Archived

eng-quality-handoff

Deliver changes with clear communication, reviewer-ready context, and follow-up accountability.

First seen May 26, 2026

Installation

$ npx skills add tjboudreaux/cc-engineering-skills --skill eng-quality-handoff

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tjboudreaux/cc-engineering-skills · top by installs.

npx skills add tjboudreaux/cc-engineering-skills

Browse all from tjboudreaux/cc-engineering-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,346 B
  • docs SUMMARY.md 122 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

Collaborative Quality Handoff

Intent

  • Make it effortless for reviewers, QA, and partners to understand, validate, and extend your work.
  • Ensure ownership persists after merge via clear action items and shared context.

Workflow

  1. Narrate the change

- Summarize problem, approach, and tradeoffs in the PR/issue using concise bullets. - Link related tickets, specs, dashboards, or smart-contract addresses.

  1. Surface review focus

- Call out risky areas, migrations, or TODOs explicitly; request specific expertise if needed.

  1. Attach evidence

- Provide test results, captures, or transaction hashes inline so reviewers don’t need to rerun everything.

  1. Plan follow-ups

- Create tasks for deferred work, debt, or experiment cleanups with owners and timelines.

  1. Stay available

- Monitor review threads, CI pipelines, and post-merge telemetry; respond quickly and document resolutions.

Verification

  • Review checklist complete (tests attached, docs/flags updated, reviewers assigned).
  • Outstanding issues tracked with owners; no “known issue” left implicit.
  • After merge, confirm deployment/monitoring links are shared with relevant teams.