preen-deferred-fixes

Implement deferred-fix issues from merged PR review threads with tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/a2f0/tearleads --skill preen-deferred-fixes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: preen-deferred-fixes
Source: https://github.com/a2f0/tearleads/tree/main/.codex/skills/preen-deferred-fixes
Command: npx skills add https://github.com/a2f0/tearleads --skill preen-deferred-fixes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of addressing deferred feedback from code reviews, ensuring that commitments are met and code quality is maintained.

Core Features & Use Cases

  • Automated Issue Tracking: Finds and processes issues labeled 'deferred-fix'.
  • Contextual Information Retrieval: Uses tools to find specific deferred commitments within PRs and review threads.
  • Implementation & Testing: Implements fixes, adds or updates tests, and validates changes.
  • Merge Preparation: Commits, pushes, and prepares the branch for merging.
  • Use Case: After a PR is merged, this Skill can automatically pick up any "TODO" items noted in the review, implement them with corresponding tests, and get them ready for the next merge.

Quick Start

Use the preen-deferred-fixes skill to find and implement all open deferred fix issues.

Frequently Asked Questions about preen-deferred-fixes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate deferred fixes from GitHub PR review threads?

Automating deferred fixes involves identifying issues labeled 'deferred-fix', retrieving context from PR review threads, implementing changes with tests, and preparing the branch for merging. This ensures merged PR feedback is addressed systematically.

What is the best way to track and implement deferred-fix issues after a merge?

Tracking deferred-fix issues requires scanning GitHub for specific labels, extracting commitments from review threads, and validating applied changes locally with tests before pushing the branch to the merge queue.

How do I ensure code review feedback marked as TODO is implemented with tests?

To ensure code review feedback is implemented with tests, retrieve the deferred-fix context, apply the code changes, add or update corresponding tests, and validate locally before committing to the branch.

Can I use GitHub CLI to retrieve context for deferred code review commitments?

Yes, GitHub CLI can be used to retrieve context for deferred code review commitments. The process identifies labeled issues, extracts thread details, implements fixes, and prepares the results for merging.

Does automating deferred fixes work with a merge queue workflow?

Yes, automating deferred fixes works with a merge queue workflow. It commits, pushes, and prepares the validated branch for merging, ensuring code quality commitments are met without manual intervention.