rebase-hygiene-audit

Audit open pull requests for rebase readiness using merge-base and conflict analysis.

3|2|Updated May 12, 2026
One-click install
npx skills add https://github.com/kriscendobot/garden --skill rebase-hygiene-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rebase-hygiene-audit
Source: https://github.com/kriscendobot/garden/tree/main/skills/rebase-hygiene-audit
Command: npx skills add https://github.com/kriscendobot/garden --skill rebase-hygiene-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the technical debt of messy pull request histories by identifying which branches are ready for a clean rebase versus those requiring manual conflict resolution.

Core Features & Use Cases

  • Automated Hygiene Checks: Scans open pull requests to categorize them by their rebase status, including clean, conflicted, or merge-commit polluted states.
  • Actionable Reporting: Generates a summary report that helps maintainers and triagers prioritize which PRs need attention without performing destructive operations.
  • Use Case: A maintainer can run this audit to quickly identify which of the 50 open feature branches can be automatically rebased and which require the author to resolve merge conflicts.

Quick Start

Run the rebase hygiene audit skill to generate a status report for all open pull requests in the current repository.

Frequently Asked Questions about rebase-hygiene-audit

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

FAQPage Schema
How do I check if an open pull request is ready for a clean rebase?

Run a read-only batch audit to evaluate branch synchronization against base references using git merge-base analysis. This categorizes open pull requests into actionable states like needs-rebase or has-merge-commits to determine rebase readiness.

What is rebase hygiene and why does my pull request stack need an audit?

Rebase hygiene identifies technical debt from messy pull request histories by detecting merge commits and branch conflicts. Auditing open PR stacks helps maintainers prioritize which branches need manual conflict resolution versus automatic rebasing.

How do I automate git merge-base conflict analysis for multiple open pull requests?

Execute a batch audit that scans open pull requests to categorize their rebase status automatically. It generates structured summary reports for triagers to quickly identify clean, conflicted, or merge-commit polluted states across all branches.

Can I identify which feature branches have merge commits without executing destructive git operations?

Yes, this read-only audit evaluates branch synchronization and categorizes pull requests without performing destructive operations. It safely identifies branches with merge commits or conflicts so authors can resolve them before rebasing.

Does the rebase readiness audit modify my repository branches during the conflict analysis?

No, the audit is strictly read-only and performs batch analysis without executing destructive git operations. It only evaluates branch synchronization against base references to generate structured reports for triagers.

What's the best way to prioritize manual conflict resolution across 50 open feature branches?

Generate a structured status report from an automated hygiene check to categorize open pull requests by rebase readiness. This allows maintainers to quickly identify which branches can be automatically rebased and which require author intervention.