Test locale- and i18n-specific browser behavior with agent-browser by forcing a non-English JavaScript runtime locale through CDP. Use when reproducing or verifying bugs involving date/time markers, number or currency separators, Intl APIs, RTL behavior, or behavior that differs under locales such as sv-SE, tr-TR…
Monitor an open pull request through CI, review feedback, conflicts, draft-to-ready transitions, and merge readiness. Use after opening a PR, when the user says "babysit this PR" or "CI is failing," or as the final stage of $ship.
Guide for building delightful, human-first command-line tools with proper command structure, output formatting, error handling, configuration, and extensibility. Use when creating CLI tools, adding subcommands, designing CLI output, handling errors in CLIs, or reviewing CLI code for UX issues.
Check design-system and UI consistency for diffs that touch user-facing surfaces. Use for visual changes, design checks, or as the UI stage of $ship, including small component, style, copy, and layout changes.
Find and fix repository documentation that a code change made false, including AGENTS.md, README files, docs, ADR references, command examples, APIs, configuration, and environment variables. Use after architectural or interface changes, renames, workflow changes, behavior-preserving refactors, or as the documentation…
Audit and improve the quality of AI-assisted, vibe-coded, branch, or work-in-progress code changes through eight specialist subagents covering duplication, type ownership, unused code, dependency cycles, weak typing, error handling, legacy paths, and code/comment quality. Use when the user requests a comprehensive…
Modern CSS best practices and patterns. Use when writing, editing, or reviewing CSS, SCSS, styled-components, or any task that produces CSS output. Provides modern alternatives to legacy hacks, JavaScript workarounds, and library dependencies.
Upload a local image through GitHub's authenticated web editor and embed the resulting user-attachments URL in a GitHub pull request or issue body. Use when the user explicitly asks to add a screenshot, comparison, diagram, or other image to a specific GitHub PR or issue. Preserve the existing body, verify the…
Commit scoped local changes, push a branch, and open a pull request following repository conventions for naming, commit format, templates, issue links, readiness, and reviewers. Use when the user asks to open a PR, commit and push, or as the publishing stage of $ship.
Rebuild a tangled feature branch into a small set of reviewer-friendly logical commits while preserving its final tree byte-for-byte. Use when asked to regroup, squash, tidy, or rewrite a branch with many interleaved feature, fixup, review, merge, or formatting commits. Resolve the actual PR base, plan groups with the…
Answer a question from primary sources and record every source checked under research/. Use when the user asks for a topic researched, for the evidence behind a claim, or when a decision needs facts you would otherwise guess at.
Take a finished local change through verification, UI checks, pull-request publication, CI and review follow-up, and the user-authorized merge outcome. Use when implementation is complete and the user says "ship it" or "get this merged," or as the final stage of $build. Do not use to implement new feature scope.
Make a behavior-preserving quality pass over changed files for reuse, clarity, types, dead code, structure, and accidental inefficiency. Use after significant implementation, before a PR, when the user asks to simplify or clean up a diff, or as the closing pass of $implement.
Transcribe audio or video files to text locally on macOS using parakeet-mlx (NVIDIA Parakeet via Apple MLX). Use when the user asks to transcribe an audio/video file, get a transcript, generate subtitles/captions (srt/vtt), or convert speech in a file to text. Triggers on "transcribe this", "make a transcript", "get…
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
Prove a change works end to end through acceptance criteria, focused project gates, real user or caller flows, edge cases, and reliability checks. Use before a PR, when the user asks whether a change actually works, or as the first stage of $ship even when automated tests are green.
Use when user says "improve my writing", "make this clearer", "edit for clarity", "copyedit", "proofread", "review my prose", or asks for help with documentation, README files, commit messages, error messages, UI text, comments, or any prose humans will read. Applies Strunk's Elements of Style rules to make writing…
Guides writing engaging technical blog posts that developers actually read. Triggers on: "write a blog post", "blog post about", "technical article", "write about [topic]", "review my blog post", "improve this article", "technical writing", "structure my post", "draft a post", "help me write", "publishing a tutorial"…
Write new prose or rewrite existing prose so it reads like the work of a thoughtful human rather than a language model. Use for documents, articles, essays, posts, reports, emails, documentation, and other prose when the user asks for natural voice, sharper editing, fewer AI tells, or removal of formulaic language…
★not rated 4 1mo agoA81 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: