Set up a project's agent instructions as a single source of truth — AGENTS.md as the real file, with CLAUDE.md (and optionally other agents' files) as symlinks to it. Use when starting/bootstrapping a repo, when asked to "add a CLAUDE.md / AGENTS.md", "set up project conventions / agent instructions", "make Claude use…
Autonomously drive a pull request to merge-ready — opening or attaching to it, then resolving automated code review (triage findings, fix the valid, reject the invalid, push, loop) and pinging a human to merge. Knows when to STOP: at diminishing returns (niche/trivial/contradictory findings, severity trending down, or…
Install GitHub Actions workflows that delete stale git branches safely — the closed-without-merging path plus a scheduled orphan sweep — and enable the native deletebranchonmerge setting that handles merged PRs. Host-agnostic: no Vercel, Neon or any external service required, works in any GitHub repo. Never deletes a…
Add a GitHub Actions workflow that posts code-size and cost statistics — lines of code, per-language breakdown, complexity, and a COCOMO "what would this cost to build" estimate — as a sticky comment on every pull request, using scc. Use when you want a per-PR code-stats or "worth of the codebase" comment, to show LOC…
The Conventional Commits format — also called "semantic commits" / semantic commit messages — a type(scope): description header (feat, fix, …) plus an optional BREAKING CHANGE footer, and how it makes history machine-readable to drive automated version bumps and changelogs. Use when writing a commit message or PR…
Review a change set with two or more independent AI reviewers in parallel — a Sonnet subagent and the CodeRabbit CLI — then merge + dedupe their findings, triage valid vs invalid, fix (directly or via parallel fix-subagents), and hand back a report of what was fixed/how and what was ignored/why. Use when asked to…
Reasoning and communication discipline modelled on Claude Fable 5's default behaviours, for Claude Opus 4.8 (or any Claude 4.x model): calibrate effort, verify before asserting, separate what you know from what you infer, and report plainly. Use when the task involves analysis, judgement, debugging, research, writing…
Trunk-based Git workflow with enforced branch naming and squash-merge PR titles, including how stacked PRs fit it. Use when setting up or standardising a branch/PR workflow, naming branches (feature/ fix/ hotfix/ and AI-agent prefixes claude/ cursor/ codex/ copilot/ codegen-bot/ dependabot/), configuring squash-only…
Create complete, analytics-ready Linear issues in ONE pass — resolve the right project (never guess it), and proactively fill the metadata that's technically optional but matters for planning/analytics: priority, estimate, labels (a Type + an Area from the team's existing taxonomy), milestone, assignee, cycle, and…
Audit an ENTIRE codebase with multiple agents in parallel — map the repo, partition it into review slices, fan out one (or more, multi-lens) reviewer subagent per slice, reduce with a cross-cutting/architecture critic + a completeness check, then triage, fix, and report with an honest coverage ledger. Use when asked…
Add locale-prefixed i18n routing across a Next.js monorepo (Turborepo / pnpm workspaces) by extracting the engine into a shared workspace package that every app consumes — locale detection + a middleware/proxy factory + a use client LocaleProvider/hooks, plus a shared supportedLanguages config. Each app redirects /…
Add locale-prefixed i18n routing to a single (non-monorepo) Next.js App Router site — a middleware/proxy that redirects / and any unprefixed path to / /… using the locale toggle's last choice (the NEXTLOCALE cookie) then the browser's Accept-Language, a [locale] layout with a LocaleProvider + hooks, and a LocaleToggle…
Cut fewer, batched releases (a 'release train') instead of one per merge — by triggering semantic-release on demand or on a cadence rather than on every push to main. Use when releasing on every merge is too noisy, when you want one larger readable changelog per release, to add a manual 'cut a release' button…
Stop every push/merge to main from shipping to production — deploy only on a real release. Use when a merge to main unexpectedly deploys to prod, when you want production to deploy only on a semantic-release version (not every commit), when setting up preview-on-feature-branch but gated-prod-on-main, wiring a Vercel…
Resolve git merge/rebase conflicts non-destructively — preserving the intent of BOTH sides — and hand off to a human when a conflict can't be resolved safely. Use when a branch or PR has conflicts with its base ('this branch has conflicts that must be resolved', GitHub mergeable=CONFLICTING / mergeStateStatus=DIRTY)…
How iOS 26 / iPadOS 26 Safari's "Liquid Glass" translucent status & address bars interact with web content, the viewport/keyboard facts behind them, and what to watch for when a design gets creative (immersive/edge-to-edge layouts, custom drawers/modals, gesture panning, themeable backgrounds, canvas). Use when an…
Automate versioning, changelog, tags, GitHub Releases, and npm publishing from Conventional Commits with semantic-release. Use when setting up or debugging automated releases, wiring a .releaserc / release config and the plugin pipeline (commit-analyzer, release-notes-generator, changelog, npm, git, github), making…
How to author and publish agent skills for the skills.sh / npx skills ecosystem — the SKILL.md format, why the frontmatter description is the trigger, multi-skill repo layout, the skills CLI (init/add/list/find/update/remove with flags), publishing to GitHub with SEO metadata, and public vs private repos (it…
A free DIY reimplementation of Vercel's $150/mo Advanced Deployment Protection add-on — all three features (Password Protection, private/prod deployments, Deployment Protection Exceptions) plus named automation bypass tokens — a middleware gate for ANY framework on Vercel (Next.js proxy, or…
Install a GitHub Actions workflow that deletes a branch's Vercel PREVIEW deployments when that branch is deleted — every deployment it accumulated, not just the aliased URL (Vercel keeps one immutable deployment per push, so a 15-push branch leaves 15 live URLs). Requires Vercel; if you just want stale git branches…
★not rated 5 12d agoA160 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: