Git & VCS
Git operations, commit helpers, branch management
MLOps Collaboration
by fmind
Guide to prepare MLOps projects for sharing, collaboration, and community engagement.
MLOps Automation
by fmind
Guide to refine MLOps projects with task automation, containerization, CI/CD pipelines, and robust experiment tracking.
MLOps Initialization
by fmind
Guide to initialize a new MLOps project with standard tools (uv, git, VS Code) and best practices.
git-commit
by davidgasquez
Create atomic commits prepended with emojis
displaying-html-in-flutter
by rodydavis
Easily display and interact with HTML content in your Flutter app using the easy_web_view package, which supports both web and mobile platforms.
color-utilities-in-javascript
by rodydavis
Explore helpful color utility functions, like RGB to HSL, HEX to RGB, and HSL to HEX, generated with the assistance of GitHub Copilot.
how-to-create-html-web-components-with-dart
by rodydavis
Discover the power of Web Components and how to build them with both JavaScript and Dart for reusable, framework-agnostic UI elements.
verify-pin-bump
by drakulavich
Use when a model SHA-256 mismatch surfaces (download_verified errors, manifest_tests failures, fresh download produces a different hash than rust/src/models.rs pins). Walks through the safe bump procedure — verify the upstream weights deliberately, then update the pin. Refuses to suggest commenting out verification.
release-cli
by drakulavich
Cuts a STABLE CLI release (vX.Y.Z-cli marker tag; not for beta or alpha markers, which this lane silently skips while burning the tag) — the 🚀 Release (CLI) lane builds the Linux packages, publishes the marker release, and dispatches npm publish with provenance. Covers version alignment across package.json and server.json, why the tag must be pushed by a human, and how to verify from the registry rather than through a stale global install. Refuses to auto-run; user must explicitly invoke. For an engine release use release-engine.
dig
by udecode
Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you don't know about. Triggers on questions like "How do I use X library?", "What's the API for Y?", "Show me how Z library handles this", or when encountering unfamiliar library usage.
changelog
by udecode
Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering.
pr
by udecode
Comprehensive GitHub pull request management - create regular/draft PRs with descriptions and commits, review PRs with severity ratings. Triggers on "create a PR", "make a draft PR", "review PR", or any PR workflow task.
reagent-migration
by day8
Rewrites Reagent VIEW code into Fresco (re-frame.fresco, alias h) — re-frame2's re-frame-native view layer: a view becomes an h/defview mounted in brackets, @(subscribe …) becomes (h/sub …), handlers become event vectors, Form-2/Form-3 state moves out of the component. First establish whether the user needs Fresco: re-frame2's Reagent adapter is first-class and supported, so a v1 app keeps its view code and needs NO rewrite to land on re-frame2 — that is re-frame-migration, and it finishes the job. This is an OPTIONAL second step, and Fresco is pre-publication with no released Maven coordinate. Do not use for: the v1→v2 events/subs/db migration (re-frame-migration), writing new re-frame2 code (re-frame2), greenfield setup (re-frame2-setup), or live-runtime inspection (re-frame2-pair). Trigger on "migrate my Reagent views to Fresco", "port this component to h/defview", or a Reagent view surface (r/atom, @(subscribe …) in a view) named in a Fresco context.
re-frame2-implementor
by day8
Guides an engineer building a NEW re-frame2 implementation in one of the eight in-scope JS-cross-compile-to-React+VDOM host languages — ClojureScript (the reference), TypeScript, Melange/ReScript/Reason, F# (Fable), Squint, Scala.js, PureScript, Kotlin/JS — over a two-phase workflow (record the port profile, then one EP loop driven by the pinned spec and live conformance fixtures, with the conformance corpus as the acceptance test). Do not use for: writing apps on the CLJS reference (re-frame2), greenfield bootstrap (re-frame2-setup), v1→v2 migration (re-frame-migration), live-app inspection (re-frame2-pair), or an out-of-scope target — a non-React substrate (Vue, Solid, Svelte, vanilla DOM) or a host that does not cross-compile to JS (Python, Ruby, native Rust, Go, server-side JVM): out of scope by deliberate spec choice, so surface the spec/000-Vision.md scope footnote and stop. Trigger on "port re-frame2", "implement re-frame2 in a language", "conformance corpus".
re-frame-migration
by day8
Migrates an existing re-frame v1.x ClojureScript codebase to re-frame2. Swaps the artefact coord (re-frame/re-frame → day8/re-frame2 + a substrate adapter), applies the mechanical (Type A) rewrites from MIGRATION.md automatically, and flags the judgment-call (Type B) call sites for human review before touching them. Do not use for: greenfield bootstrap, writing v2 application code, live v2-app inspection, static critique, devtools tours, or porting re-frame2 itself — see the full routing table in skills/README.md §Skill routing for the right sibling skill. Trigger on phrasing like "migrate to re-frame2", "upgrade re-frame", "v1 to v2", "what breaks under re-frame2", or any prompt referencing a v1 surface (re-frame.db, dispatch-with, reg-global-interceptor, reg-sub-raw, ^:flush-dom, re-frame.alpha, re-frame-test, old top-level :dispatch / :dispatch-n effect-map keys), or a v1 add-on library (http-fx / :http-xhrio, async-flow-fx / :async-flow).
rust-onboard
by thrashr888
Onboard a new Rust project with standard tooling, CI/CD, and best practices. Use when starting a new Rust project or setting up an existing one with proper infrastructure.
makefile-patterns
by thrashr888
Makefile patterns for development workflows. Use when creating or understanding Makefiles for build automation, release workflows, and development iteration.
github-releases
by thrashr888
Create releases for Rust CLI tools, macOS apps, Python/uv projects, and Next.js apps. Use when asked to release, tag, ship, publish, or deploy any project.
plain-upgrade
by dropseed
Upgrades Plain packages and applies required migration changes. Use when updating to newer package versions.
release
by dropseed
Releases Plain packages with intelligent version suggestions and parallel release notes generation. Use when releasing packages to PyPI.
wireit
by forcedotcom
Author and use Wireit scripts for npm. Use when working with Wireit configuration, npm scripts, build pipelines, or when the user mentions Wireit.
pr-draft
by forcedotcom
Draft PRs with conventional commit-style titles and Gus work item refs. Use when drafting PRs, PR titles, PR descriptions, opening PRs, or Git2Gus workflows.
plain-install
by dropseed
Installs Plain packages and guides through setup steps. Use when adding new packages to a project.
generating-changelogs
by alunadev
Transforms technical git commits into polished, user-friendly changelogs. Use when preparing release notes, creating product update summaries, documenting changes for customers, or maintaining a public changelog page.