codex-finding-resolution
bybdouble· 16 skills
Use when Codex review returns findings, when processing codex_review_and_fix or codex_review results, when collecting a codex-delegate job with codex_status/codex_result, when cross-model review report contains P0-P3 items, or when about to post a Codex review report to Linear. Also use when about to file a Codex finding as a follow-up ticket (use the SCOPE_EXPANSION_ESCAPE rules), when about to skip a P1 or P2 finding with rationale like "complex / tricky / needs more thought" (these are disqualifying — fix it now), when about to file P3 findings as tickets (P3 → closure-log only), or when about to pause Codex review for mid-flow user input (the flow is hands-off; agent applies impact-bar autonomously). Use in both /epic-swarm and /execute-ticket workflows.
How to install codex-finding-resolution?
bdouble/pm-vibecode-ops/codex-finding-resolution
$npx -y skills add bdouble/pm-vibecode-ops --skill codex-finding-resolutionInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/bdouble/pm-vibecode-ops" --skill "bdouble/pm-vibecode-ops/codex-finding-resolution"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/bdouble/pm-vibecode-ops" that are relevant to the current task. Run `npx skills add "https://github.com/bdouble/pm-vibecode-ops"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
