git-commit
Commit work the right way by gathering full repo state, respecting the project's commitlint/pre-commit/branch rules, staging only understood files, and writing…
A skill ships with its plugin and fires as you prompt.
33,758 skills across 2,137 plugins. 142 of them fire as you prompt.
Showing 48 of 208
Commit work the right way by gathering full repo state, respecting the project's commitlint/pre-commit/branch rules, staging only understood files, and writing…
Recover safely from Git mistakes such as discard, unstage, amend, reset, revert, restore lost commits via reflog, recover deleted branches, and fix bad…
Use when reproducing, isolating, and fixing a bug with the smallest safe change.
Use when a build, test, type check, or lint is failing — locally or in CI — and the fix must be the smallest safe diff with no opportunistic refactors or…
Use when routing a prompt to a local provider CLI for a second opinion, review, or plan -- you are about to call a provider directly, need the response saved…
Set up an isolated workspace for feature work so the current branch and working tree stay untouched — detecting existing isolation first, preferring the…
Generate or repair a .gitignore tailored to the project's actual stacks, frameworks, OS, and editors, and untrack files that are already committed but should…
Relentlessly stress-test a plan, design, architecture, idea, or strategy until all critical decisions are resolved. Use when a plan, design, or decision needs…
Use before submitting a PR or considering a task done to evaluate the blast radius of your changes -- you touched a public signature, a shared utility, a…
Use when preparing release notes or a changelog entry from commits, PRs, or diffs, summarizing a sprint or version range, or scanning a range for breaking…
Use when a CI pipeline has failed and the real error must be extracted from thousands of lines of noisy logs.
Stress-test a plan against the project's existing domain model by challenging terminology, surfacing contradictions with code, and updating CONTEXT.md and ADRs…
Compact the current conversation into a handoff document for another agent to pick up. Use when ending a session, switching agents, or preserving context…
Turn a rough bug report, idea, or complaint into a well-formed, actionable issue - investigating the codebase first to add reproduction steps, expected vs…
Use when a wide refactor or migration is too large to ship as one change — API renames across many files, framework or config migrations, or mechanical…
Use when conversation context is bloated, constraints are being forgotten, or a compact handoff is needed before continuing work.
Use when a subsystem needs persistent context for future agents or engineers -- its boundaries keep being rediscovered the hard way, invariants keep getting…
Resolve Git merge, rebase, cherry-pick, revert, and stash conflicts safely by understanding both sides and the operation in progress before integrating, then…
Review code being written or modified against the OWASP Top 10:2025 and ASVS secure-coding requirements, catching vulnerability classes before they ship. Works…
Fan independent work out to multiple subagents that run concurrently, each with a focused scope and self-contained instructions, then review and integrate…
Use when a task runs long and the context window is filling -- large files are being read whole, command output is flooding the transcript, or responses are…
Use when starting work in an unfamiliar area of a codebase, spawning a subagent that needs targeted file context, a first search pass missed the relevant file,…
Use when adding or reviewing data quality tests for dbt models in warehouse-backed analytics projects. Covers dbt generic tests, singular tests (assert_*.sql),…
Optimize a performance problem by profiling to find the real bottleneck before changing anything, making one targeted change, and verifying both the…
Generate a clear, reviewer-friendly pull-request description from a diff, covering what changed, why, risk, and how it was tested. Use when opening a pull…
Cut a release by determining the SemVer bump from history, updating version files across any stack, refreshing the changelog, creating an annotated (optionally…
Use when reviewing how data is split into train/validation/test sets -- especially with time-series data, repeated entities (users, patients, sessions), or…
Use when reviewing a new or changed dbt incremental model -- the strategy looks over-engineered, rebuild or delete behavior is unclear, or the model deviates…
Use when a dbt change needs preflight before a PR, review, or merge -- changed models, snapshots, seeds, macros, or semantic YAML whose blast radius and test…
Scan code or a diff for hardcoded secrets (API keys, tokens, passwords, private keys, and other exposed credentials) before they get committed or shipped. Use…
Apply the SOLID principles as design diagnostics when writing, reviewing, or refactoring code with classes, modules, or service boundaries - detecting god…
Generate a standup or weekly-review update from actual work evidence - commits, branches, PRs, and issues across one or more repositories - grouped into done /…
Use when creating or modifying dimensional dbt models in warehouse-backed analytics projects. Covers a four-layer warehouse architecture…
Use when unused functions, classes, exports, or files need to be identified and safely deleted.
Use when the user provides a URL to a standard web page and clean Markdown extraction with Defuddle would reduce clutter and token cost.
Debug a bug, test failure, crash, or unexpected behaviour by finding the root cause before changing anything, instead of guessing at fixes. Works in any…
Implement a feature or bugfix test-first using the red-green-refactor cycle — write a failing test, watch it fail, write the minimal code to pass, then clean…
Gate every "it works / it's fixed / tests pass / done" claim behind fresh evidence — run the actual verifying command, read its output, and only then state the…
Use when package manifests carry unused or redundant third-party dependencies that slow builds, widen the security surface, or complicate updates.
Use when a release spans multiple systems or vendors, order of operations matters with rollback planned up front, or a failed step in one system could corrupt…
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Verify a web application works correctly in a real browser using Playwright. Covers page navigation, form submission, user interactions, console error…
Turn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context. Breaks…
Use when documentation may have rotted against the code -- files were renamed or moved, scripts or env vars changed, or readers report commands and paths from…
Use when apx commands fail or assets are missing from listings, MCP servers fail to start, builds hit command-not-found or module-not-found errors, generated…
Use when reviewing ML training code to confirm a run could be reconstructed later -- hyperparameters, metrics, data references, and artifacts logged, not just…
Use when confronted with an unknown failure in CI or production, before committing to a deep debugging approach.
Use when designing or reviewing filesystem MCP access, path boundaries, allowed roots, method allowlists, and safe local file operations.
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic