Use it at the exact level you need
Review one risky method or an entire file. No need to wait for a full PR cycle to get useful feedback.
VS Code / Cursor extension
Vibe code freely. MergeCore catches what seniors would flag.
Review a snippet, file, or git diff inside VS Code and Cursor. MergeCore spots risky Laravel mistakes, weak AI-generated code, and messy logic — then helps you fix it before review begins.
The workflow
Review code where it actually matters: before commit.
Run MergeCore on a snippet, file, staged diff, or working tree. Get actionable findings, severity scores, Laravel-aware feedback, and rewrites you can apply immediately.
MergeCore: Review Selection · Review Active File · Review Git Diff · Review Staged DiffIt is built for the moment confidence drops: after the code works, before someone else has to review the mess.
Why it helps
Fewer pointless PR comments. Better code shipped faster.
MergeCore is strongest today in Laravel and PHP-heavy workflows, and it reads project signals from the repo so the feedback feels closer to a sharp engineer than a generic AI lint pass.
See issues where you're already working
Findings appear inside the editor, so you can fix problems while context is still fresh.
Review before team overhead
Catch weak assumptions, rough edges, and AI sludge before someone else has to point it out.
Get feedback that leads somewhere
Not vague complaints. Real findings, code examples, and practical rewrites.
Apply improvements instantly
Accept patches directly in-editor or export a markdown review for your team.
Built for modern stacks
Laravel first. Also understands Filament, Pest, Livewire, TypeScript, React, Vue, and modern PHP workflows.
// Rule Packs
Current rule packs, plus the next wave on the roadmap.
Shipping today from the repo: Laravel Core, Filament, Pest, Livewire, and Alpine. Planned next from the roadmap: TypeScript, React, Node, Python, Go, and deeper Laravel ops coverage.
Current rule packs
Laravel Core
Production rules
Filament
Admin & panels
Pest
Testing rules
Livewire
Component behaviour
Alpine
Blade frontend rules
Future rule packs
TypeScript
App & service rules
React
Frontend review packs
Node
Backend JS services
Python
Services & data work
Go
Modules & APIs
Horizon & Octane
Deeper Laravel ops
How Packs Work
Rule packs are structured, not hand-wavy.
MergeCore packs are made of a few clear files with different jobs: one says what the pack is, one defines the rules and scoring, one gives human shorthand for common problems, and one explains how an AI reviewer should apply the pack in practice.
Manifest & wiring
pack.json
The pack manifest tells MergeCore what the pack is called, which version it is, which files it publishes, and how hosts should resolve the rest of the pack.
- Defines metadata like pack ID, title, version, tags, and compatibility details.
- Points at the files the pack exposes, such as rubric, smells, and agent instructions.
- Acts as the single lookup point when a host wants to load the pack correctly.
Rules & scoring
rubric.json
This is the scoring source of truth. It defines the rules, severities, penalties, and detection hints that shape how MergeCore judges a change.
- Holds stable rule IDs, categories, titles, descriptions, and severity levels.
- Controls how findings affect score so review output stays consistent and traceable.
- Lets packs gate or tune rules for stack-specific contexts like Filament or Pest.
Human-facing shorthand
smells.json
The smell index translates deeper rules into named patterns people recognise quickly, which helps with triage, wording, and fix guidance.
- Maps named smells back to rubric rules through rule references.
- Adds quick summaries, layers, and typical-fix guidance for common problems.
- Keeps reviewer wording practical without losing the rule-level source underneath.
How reviewers should think
agents.md
Agent instructions explain tone, priorities, evidence rules, and how the reviewer should apply the pack instead of just dumping raw rule text.
- Defines stance like security before style and evidence before invention.
- Keeps AI-assisted review aligned with the same language and standards across teams.
- Bridges the gap between structured rules and useful, readable feedback.
Entry points
Run review exactly where confidence drops.
Use MergeCore on the part of the change that feels risky, messy, or just too AI-written to trust on the first pass.
Selection review
Perfect for a risky block, fresh refactor, or the method that feels fine until you look twice.
Active file review
Run a full pass when the whole file needs a proper sanity check, not just one highlighted section.
Working tree diff review
Check your in-progress branch before it turns into a pile of fixes, follow-ups, and reviewer comments.
Staged diff review
Give the exact staged patch one last senior-style pass before you commit it or send it up for review.
Fits your setup
Easy to try. Serious when you need it.
The extension is designed so you can get a feel for the workflow immediately, then connect it to your configured MergeCore API environment when you are ready for the full backend-driven path.
- Start without ceremony. You can install the extension and get through the review workflow without first wrestling with account setup, tokens, or external plumbing.
- Connect your review backend when ready. When you want MergeCore running against your configured API, add your base URL and token in settings and switch the extension over to that path.
- Stay in flow. The Review panel can open automatically after a run, and it can fall back to a beside tab when the activity-bar view is not available in your editor host.
Write fast. Review smart. Merge confidently.
Give the branch one last senior pass before review starts, and catch the stuff that makes people lose confidence fast.
See It Catch Real Issues