Supercharge Your Git Workflow with Laravel Commit‑Lint

Mubbasher Ahmed Qureshi — Tue, 29 Jul 2025 13:38:13 +0000

Tired of messy, inconsistent commit messages cluttering your Git history?

Say hello to Laravel Commit‑Lint — a lightweight, developer-friendly Laravel package built to enforce Conventional Commits right from your terminal.

Crafted by Mubbasher Ahmed Qureshi (@mubbi), this tool brings structure, readability, and automation to your Git commits—without any complex setup or bloated dependencies.

🧠 Why Commit Linting Even Matters

Before diving into features, let’s answer a critical question:

“Isn’t this just extra work?”

Actually, it’s the opposite.

Standardizing commit messages makes your Git history predictable, changelogs automated, and team collaboration smoother. It also plays perfectly with tools like semantic versioning and CI/CD pipelines.

And Laravel Commit‑Lint brings all of this goodness—natively—to your Laravel workflow.

📦 What Is Laravel Commit‑Lint?

Laravel Commit‑Lint is a plug-and-play package that installs a commit-msg Git hook in your Laravel project. Every time you commit, it validates your message against the Conventional Commits format:

<type>(<scope>): <short description>

No valid format? The commit is blocked—with helpful feedback to fix it.

✅ feat(auth): add login endpoint

❌ updated stuff

And don’t worry—special commits like merge, WIP, or revert are automatically skipped.

⚙️ Key Features

🔍 Real-time commit validation – Catch bad messages before they hit your repo.
⚡ Zero-config Artisan install – Just run php artisan commitlint:install.
🚫 Smart skipping – Merge, WIP, and revert commits are ignored.
🛠 Customizable hooks – Install to a custom path or use your own stub.

🚀 Getting Started

1. Install the Package

composer require mubbi/laravel-commit-lint --dev

2. Install the Git Hook

php artisan commitlint:install

That’s it. You’re live.

Want a custom hook path?

php artisan commitlint:install /your/custom/path

Or maybe a custom hook script?

php artisan commitlint:install --stub=/path/to/your/hook.stub

🧪 Try It in Action

git commit -m "fix(user): handle null emails"
# ✅ Success

git commit -m "fixed stuff"
# ❌ Rejected – helpful message shown

git commit -m "WIP: experimenting with Stripe"
# ✅ Skipped – WIP commit allowed

💡 Real-World Use Case: Why This Exists

While contributing to the Laravel core, I proposed PR #56443 to introduce commit linting as a built-in feature. The Laravel team appreciated the idea, but Taylor Otwell preferred keeping the core minimal—so I released it as a standalone tool.

Now, Laravel devs can still enjoy structured commit messages—without touching the framework itself.

🧰 Valid vs Invalid Commit Messages

✅ Valid Examples

feat: add user registration
fix: correct timezone offset
chore: clean up config files
docs(readme): update usage guide

❌ Invalid Examples

fixed auth
update stuff
bug fix
done

When a message is invalid, you’ll see a helpful explanation and suggested fixes—so you can commit confidently.

🧯 Troubleshooting & Tips

🔐 Permission issues? Run:

chmod +x .git/hooks/commit-msg
📂 Custom path errors? Ensure the directory exists and is writable.
🌀 Artisan command not found?

Run composer dump-autoload.
🧪 Need flexibility? Customize the hook stub and format to match your team’s standards.
❌ Want to remove it?

Delete the hook file or run:

  composer remove mubbi/laravel-commit-lint

🧭 Final Thoughts

Laravel Commit‑Lint is a no-nonsense tool for teams who value:

✅ Clean, consistent Git logs
✅ Seamless automation (semantic versioning, changelogs, CI)
✅ Laravel-native tooling—no Node or external dependencies

It’s especially perfect for Laravel 12+ teams that want structure without sacrificing speed.

🔗 Ready to Try?

Add it to your project today:

composer require mubbi/laravel-commit-lint --dev
php artisan commitlint:install

Visit the repo: github.com/mubbi/laravel-commit-lint

Turning AI Struggles into Standards — The Birth of Copilot Instructions

Mubbasher Ahmed Qureshi — Wed, 25 Jun 2025 05:42:08 +0000

In this article, I share how constant frustration with inconsistent AI coding suggestions led me to create Copilot Instructions — a simple but powerful way to turn AI struggles into clear project standards. Instead of explaining the same coding preferences over and over, I realized we can guide AI like we guide human teammates: with written instructions. That’s exactly what .github/copilot-instructions.md does. I’ve even provided ready-made templates for Laravel, React, PHP, and more, so teams can quickly align AI tools like GitHub Copilot with their coding style. The whole point? Less frustration, more consistent code, and AI that actually understands your project.

Story Link: Medium Article Link

What you guys do for your AI Assistance?

DEV Community: Mubbasher Ahmed Qureshi