finishing-a-developmen…
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
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
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting…
Use when tests pass and fail intermittently without code changes, or a test passes alone but fails in the full suite.
Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review…
Use when a GitHub PR shows failing checks and a clean failure readout is needed before changing any code.
any input (code, docs, papers, images) → knowledge graph → clustered communities → HTML + JSON + audit report. Use when the user wants to build, inspect, or…
Use when ending a session, handing a task back to the user, or approaching the context limit with work unfinished -- the next session or engineer must be able…
Use when a tricky bug, non-obvious workaround, hidden gotcha, or undocumented behavior took real debugging effort to discover and should be captured as a…
Use when a hook is about to be enabled or modified -- a hook recipe proposed for activation, a pre/post-tool or lifecycle hook added to agent settings, a git…
Use when a bug fix or complex debugging session concludes and a blameless post-mortem summary is needed for human review.
Use when migrating APIs, libraries, or patterns across a large codebase and a single mega-commit would be too risky to review or merge.
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind…
Use when querying, ingesting, or maintaining a local RAG MCP corpus for semantic document retrieval with privacy controls.
Use when debugging complex runtime failures, distributed systems, or issues where a local debugger cannot be attached.
Use when connecting to a managed codebase-context MCP/session service, checking stale maps, or safely using MCP-provided repository context.
Use when the user provides a MarkItDown-supported file or URL and converting it to Markdown first will make inspection easier, cheaper, or more reliable.
Use when an MCP server is about to be enabled, added to agent config, or upgraded -- a staged server config is a candidate for activation, a third-party server…
Design high-quality MCP servers around workflows, narrow schemas, context-aware outputs, and actionable errors. Use when building or reviewing MCP tools for…
Use when a user needs to build or refresh persistent graph memory from a mixed corpus and the right path may include graphify, incremental update, or helper…
Use when deciding the lowest-cost context path for a mixed corpus, especially when choosing among direct reading, helper conversion, graph build, graph update,…
Use when a graph already exists and the user needs retrieval, tracing, explanation, or gap detection from graph memory before reopening the full corpus.
Use when a change may affect metrics, semantic models, dashboards, reporting, or stakeholder-facing KPIs and you need to know whether business meaning or…
Use when a bug must be isolated from a large application into a standalone, runnable script or single test case.
Use when reviewing ML preprocessing or feature pipelines for target leakage -- validation metrics look suspiciously good, transformers are fitted before…
Use when writing or reviewing a model evaluation report -- accuracy is being quoted alone, or stakeholders need failure modes, segment performance, and…
Use when selecting a model for a new task or subagent, deciding whether to escalate after a failed attempt, or designing a multi-agent pipeline with mixed task…
Use when naming conventions or file structure drift across a project and need to be made consistent without changing business logic.
Ultra-compressed communication mode. Cuts token usage ~75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use when user…
Use when latency matters and several independent tasks can run at once -- a bounded implementation or investigation that needs waves of concurrent workers, not…
Use when a task must run to verified completion rather than best effort -- the user says "don't stop", "must complete", "finish this", or "keep going until…
Use when a pull request needs one bounded review and CI triage cycle with explicit approval before edits or remote writes.
Use when open pull requests, stale branches, or review bottlenecks need prioritization from current repository state.
Use when a release candidate needs final checks before tagging, publishing, or production deployment.
Use when evaluating prompts, LLM outputs, red-team suites, or model behavior with local eval configs and safe provider/cost controls.
Use when a README cannot be followed verbatim -- setup or test commands fail or are vague, environment requirements are unstated, or a new engineer or agent…
Use when receiving code review feedback, before implementing suggestions — requires technical verification and reasoned pushback, not performative agreement or…
Use when creating or reviewing red-team eval plugins, attack templates, grader rubrics, safety fixtures, or model-risk test metadata.
Use when a bug was recently introduced but you don't know which commit caused it.
Use when another local agent needs a one-shot Claude CLI answer without cross-turn relay memory.
Use when another local agent needs a one-shot Codex CLI answer and interactive behavior is acceptable or controlled.
Use when the task is to understand an unfamiliar codebase, locate key entry points, or summarize architecture before editing.
Use when reviewing or modifying ML training scripts that must produce identical results across runs or machines -- runs with the "same" config differ, or a…
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
Use when an implementation request is vague or underspecified and needs structured clarification before coding -- the user says "interview me", "ask me…
Use when mining PR review comments and text diffs for reusable writing, documentation, tone, and editorial improvement patterns.
Use when reviewing a PR or your own change plan and you need to decide how much scrutiny it deserves -- the diff touches auth, payments, crypto, migrations, or…
Use when code needs restructuring without changing observable behavior.
Use when about to add a new helper, utility, or abstraction, a task sounds like a solved problem, a new external dependency is being considered, or custom code…
Use when about to commit, push, or publish -- staged changes touch config or environment files, generated artifacts (relay sessions, logs, build output) are…
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic