conejo-merge

Implement pull request comments with gate-based verification and test-first development.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill conejo-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conejo-merge
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/conejo-merge
Command: npx skills add https://github.com/arthrod/conejo-skills --skill conejo-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, pytest, ruff, vitest, biome, cargo, and includes references (resource) components.

What problem does it solve?

This skill eliminates the common failure mode of batch-reviewing PRs, where critical insights are lost in the noise. It enforces a rigorous, gate-based implementation process that ensures every single comment is addressed, verified, and reconciled.

Core Features & Use Cases

  • Individual Comment Gating: Forces a verdict for every single comment, preventing the "skim and summarize" trap.
  • Hidden Gems Discovery: Prioritizes weird or pedantic comments, treating them as potential knowledge leaks from different training corpora.
  • Calm Implementation: Provides a structured, methodical workflow for testing, installing dependencies, and shipping fixes one task group at a time.

Quick Start

Use the conejo-merge skill to implement all comments on the pull request at the provided URL.

Frequently Asked Questions about conejo-merge

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

FAQPage Schema
How do I automate GitHub pull request comment implementation methodically?

Automate pull request comment implementation by pulling all PR comments, grouping them into actionable tasks, and executing fixes with mandatory test-first development using a gate-based verification process for each item.

What is the best way to ensure every code review comment is addressed without missing critical feedback?

To ensure every code review comment is addressed, use individual comment gating to enforce a strict verdict for each item, preventing the skim and summarize trap and prioritizing pedantic comments as potential knowledge leaks.

Do I need GitHub CLI and specific testing frameworks to automate PR fixes?

Yes, automating PR fixes requires the GitHub CLI to pull comments and project-specific testing frameworks like pytest, vitest, or cargo to enforce test-first development and ensure technical correctness during the implementation process.

How does test-first development apply to addressing GitHub PR review comments?

Test-first development applies to PR review comments by making tests mandatory before executing fixes, ensuring that every individual code review item is verified, reconciled, and technically correct within a structured workflow.

Can I use this agentic workflow to batch review and fix multiple pull request comments at once?

Yes, this agentic workflow pulls all PR comments and groups them into actionable task groups, allowing you to ship fixes methodically one task at a time while maintaining a calm, structured implementation process.