affinage

Triage pull request review comments, CI failures, and merge conflicts into graded reports.

15|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/paulnsorensen/easy-cheese --skill affinage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: affinage
Source: https://github.com/paulnsorensen/easy-cheese/tree/main/skills/affinage
Command: npx skills add https://github.com/paulnsorensen/easy-cheese --skill affinage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

It helps you efficiently triage a pull request’s review comments, failing CI checks, and merge conflicts, then decide which issues are worth acting on.

Core Features & Use Cases

  • Review + CI + Conflict triage: Grades each claim through the same “/age lens” used for fresh review.
  • Routes outcomes to the right next step: Pushes grounded issues into /cure while drafting push-backs or investigation notes when appropriate.
  • Handles merge conflicts via melt: Detects conflicting PRs and hands off to /melt instead of trying to resolve manually.

Quick Start

Run /affinage <pr-url-or-number> to generate an affinage report, draft the right reviewer replies, and (when safe) dispatch the recommended /cure fixes.

Frequently Asked Questions about affinage

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

FAQPage Schema
How do I triage pull request comments and failing CI checks together?

Pull request triage consolidates review comments, failing CI status, and merge conflicts into a single report. The affinage process grades each finding into severity buckets via the gh CLI, then routes grounded issues to automated fixes while drafting reviewer replies.

What is the best way to automate responses to code review feedback on GitHub?

Automating code review feedback responses involves fetching PR comments via gh, grading them by severity, and drafting safe push-backs or investigation notes. This workflow generates replies directly tied to the technical validity of each review claim.

How do I handle merge conflicts detected during pull request triage?

Merge conflicts detected during PR triage are routed to a dedicated melt workflow rather than resolved manually. This handoff identifies conflicting branches and initiates targeted conflict resolution without direct human intervention.

Do I need Python and the GitHub CLI to automate pull request triage?

Yes, Python3 and the GitHub CLI (gh) are required dependencies. The skill uses gh to fetch PR status and comments, while Python3 executes the grading logic that categorizes review findings into actionable severity dimensions.

How does PR triage decide which review comments need action versus push-back?

PR triage applies an age grading lens to evaluate each review claim's validity. Grounded issues are pushed into automated cure workflows for fixes, while ungrounded feedback triggers drafted push-back replies or investigation notes with safe gating.

Can I route failing CI builds and code review issues through the same workflow?

Yes, failing CI builds and code review issues are graded through the same triage lens. The workflow fetches both PR statuses and comments, categorizes them by age dimensions and severity, and dispatches automated fixes when safe.