Reviews, fixes, and prepares a git branch for final human review with a clean PR.
npx skills add https://github.com/VladSez/easy-invoice-pdf --skill merge-ready
Please help me install this Agent Skill. Skill: merge-ready Source: https://github.com/VladSez/easy-invoice-pdf/tree/main/.agents/skills/merge-ready Command: npx skills add https://github.com/VladSez/easy-invoice-pdf --skill merge-ready
Getting a branch from "code exists" to "ready for review" requires tedious manual work: syncing with main, auditing changes across multiple risk axes, running CI checks, and writing a clear PR description. This Skill automates that entire pre-merge workflow while keeping the final merge decision with a human reviewer.
pnpm ci:check (prettier, knip, tsc, oxlint) in a loop until clean.Tell the agent to make the current branch merge-ready so it reviews all changes against origin/main, fixes verified findings, and opens an updated pull request.
High-intent search queries and answers about installing and using this skill.
Invoke the merge-ready workflow on your branch. It syncs with origin/main, runs parallel review subagents across five risk axes, verifies each finding adversarially, applies fixes in checkpoint commits, and opens or updates a PR with a review guide.
Five parallel reviewers examine unnecessary complexity, security issues like authz and SSRF, billing and metering leaks, adherence to TanStack and project idioms, and vibe-coded cruft such as dead code and stale comments. Each finding includes file:line, severity, and rationale.
No. The workflow explicitly never merges the PR. It pushes the branch, updates the PR description with a summary and review notes, and reports back so the human reviewer always makes the final merge decision.
Every blocker and should-fix finding is sent to a separate verification subagent that adversarially checks it against the actual code and returns APPLY, APPLY-MODIFIED, or REJECT. Rejected findings are dropped, and nitpicks are reported without mandatory fixes.
The branch must pass pnpm ci:check, which runs prettier, knip, tsc, and oxlint. The workflow fixes failures and re-runs the check in a loop until clean, with a quick re-review for any substantial fix.
Yes. Review scope includes the committed diff against origin/main, staged and unstaged changes, and every in-scope untracked file, so newly created files cannot escape review.
paulundAutomate Git commits, pushes, and pull request creation from a new branch.
agentic-inPrepare, review, and merge GitHub pull requests with validation.
deandumAuthor and maintain project constitutions codifying invariants across specs and reviews.
liminal-aiOrchestrate six parallel specialized code reviewers into a single verified report.