docs: format Mergify policy plan

[KooshaPari]

User description

Follow-up to #544: applies the repository Prettier formatting required by hosted Lint & Format to the policy plan. No policy behavior or source changes.\n\nLocal evidence: npx --no-install prettier --check docs/superpowers/plans/2026-08-29-mergify-no-human-review.md, YAML parse, and policy invariant all pass.

---

CodeAnt-AI Description

Allow pull requests to merge automatically after required checks pass without human approval

What Changed

• Mergify can now squash-merge open, conflict-free pull requests when the configured CI, lint, and type checks succeed
• Human approval and reviewer-completion requirements no longer block automatic merging or the ready-to-merge label
• Required checks, conflict protection, pull-request-only integration, and existing labeling safeguards remain in place

Impact

✅ Faster pull request merges
✅ No approval-related merge blocks
✅ CI-gated main branch protection

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	9ac84f1	Aug 29, 2026 · 05:12	05:12

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[coderabbitai]

Warning

Review limit reached

Next included review available in 50 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e048318f-0d1e-4c42-9b40-76c442dcb8d1

📥 Commits

Reviewing files that changed from the base of the PR and between 7fd1a32 and 9ac84f1.

📒 Files selected for processing (3)

• .mergify.yml
• docs/superpowers/plans/2026-08-29-mergify-no-human-review.md
• docs/superpowers/specs/2026-08-29-mergify-no-human-review-design.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[KooshaPari]

Superseded by #546. #545 was intentionally preserved as a branch, but it inherited pre-squash #544 history and GitHub reported a content conflict; #546 is the equivalent clean one-file follow-up from current main.