skills.rest
loomantix
loomantixOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-grill

Review open pull requests with a secondary engine and push signed fixes.

2|Updated May 10, 2026
Search Tags:#automation#git#code review#pull request#github#adversarial testing
One-click install
npx skills add https://github.com/loomantix/codex-platform --skill pr-grill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-grill
Source: https://github.com/loomantix/codex-platform/tree/main/.codex/skills/pr-grill
Command: npx skills add https://github.com/loomantix/codex-platform --skill pr-grill

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill addresses the blind spots inherent in single-engine code reviews by orchestrating a secondary, adversarial deep-review pass on existing pull requests to catch design-level issues and logic flaws.

Core Features & Use Cases

  • Cross-Engine Relay: Leverages a different AI model to scrutinize design decisions, abstractions, and trade-offs that the original authoring engine may have overlooked.
  • Automated Fix Ledger: Automatically applies fixes for identified issues, pushes them to the PR head branch, and resolves threads with validation results.
  • Safety-First Workflow: Ensures all changes are signed, avoids force-pushes, and maintains a clear audit trail of the cross-engine review process.

Quick Start

Run the pr-grill skill followed by the pull request number to initiate a deep adversarial review and automated fix relay on the specified branch.

Frequently Asked Questions about pr-grill

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

FAQPage Schema
How do I run an adversarial code review on a GitHub pull request?▼

To run an adversarial code review on a GitHub pull request, use a cross-engine relay to fetch the PR head branch, scrutinize design decisions with a secondary AI model, and push verified fixes back to the remote repository.

Do I need the GitHub CLI and local Git configuration for automated pull request fixes?▼

Yes, you need the GitHub CLI and local Git configuration for automated pull request fixes. These dependencies enable secure commit signing, branch fetching, and auditable code relay without force-pushes to the remote repository.

Can I automatically push fixes back to an open PR branch after a code review?▼

Yes, you can automatically push fixes back to an open PR branch after a code review. The workflow applies an automated fix ledger, pushes changes to the PR head branch, and resolves conversation threads with validation results.

How does cross-engine adversarial testing improve pull request quality over single-engine reviews?▼

Cross-engine adversarial testing improves pull request quality by leveraging a different AI model to scrutinize design decisions and trade-offs, identifying logic flaws and abstractions that the original authoring engine inherently missed.

What are the safety limitations of using an automated fix relay on open GitHub PRs?▼

The safety limitations of an automated fix relay involve avoiding force-pushes to maintain a clear audit trail and requiring local Git configuration for secure commit signing, ensuring all cross-engine review changes are auditable and safe.

Related Skills

Explore More Software Engineering Skills→
rawvegrawveg
40

github-issue-fetcher

Fetch GitHub issues from the current repository using gh and jq.

Community
Advanced
StarrySerendipityStarrySerendipity

push-to-pr

Push local commits to an existing PR's source branch via GitHub API.

Community
Advanced
shekerkammashekerkamma

llm-council

Run multi-advisor peer review to validate high-stakes decisions.

Community
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced