Generate a .gitignore Tailored to Your Tech Stack
Your default .gitignore is probably missing half the things it should ignore — OS junk, editor artefacts, build caches. Tell Claude your exact stack and it'll write one that actually covers everything.
Generate a comprehensive .gitignore for a Laravel 11 project
using Vite, Docker, and PhpStorm as the IDE. Include OS files
for macOS and Windows.
Claude will produce a well-organised file with sections for each layer of your stack — framework files, editor configs, build output, environment files, and OS noise — with comments explaining each section.
The same approach works for any combination:
Write a .gitignore for a Next.js 14 project using Vercel
deployment, Prisma ORM, and VS Code.
You can also paste your existing .gitignore and ask Claude to audit it: "What am I missing for a project using these technologies?" It will flag the gaps and explain why each entry matters.
A proper .gitignore takes five minutes to generate and saves years of accidental commits — let Claude do it for you.
Log in to leave a comment.
The /security-review command scans your uncommitted changes for injection vectors, auth gaps, hardcoded secrets, and other common vulnerabilities.
The SessionStart hook fires when any session begins or resumes, making it ideal for loading environment variables and running one-time setup scripts.
Ask Claude to write property-based tests for your functions using fast-check — it identifies the mathematical invariants in your code and generates tests that cover inputs you'd never enumerate by hand.