Depuració
Detecció i correcció de problemes i anàlisi d’errors
behavior-preservation-checker
ArabelaTso
Compare runtime behavior between original and migrated repositories to detect behavioral differences, regressions, and semantic changes. Use when validating code migrations, refactorings, language ports, framework upgrades, or any transformation that should preserve behavior. Automatically compares test results, execution traces, API responses, and observable outputs between two repository versions. Provides actionable guidance for fixing deviations and ensuring behavioral equivalence.
ruthless-reviewer
HydraDragonAntivirus
Ruthless technical code and writing reviewer. Use this skill when the user shares code or writing and asks for feedback, review, critique, correction, "look at this", "what do you think" or similar. No flattery, no "you're right", no "great job". Only honest technical critique and a corrected version. Supports all programming languages and writing types. English and Turkish supported.
log-summarizer
proflead
Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.
observability-setup
proflead
Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.
linter-fix-guide
proflead
Explain lint errors and propose fixes. Use when a junior developer needs help resolving common lint or format warnings.
error-message-explainer
proflead
Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.
cli-ux-improver
proflead
Improve CLI help, errors, and output. Use when a mid-level developer needs to make a CLI friendlier.
performance-trace-guide
proflead
Guide collection and analysis of performance traces. Use when a mid-level developer needs to diagnose slowness.
decisive-action
athola
Guidance on when to ask clarifying questions vs proceed with standard
response-compression
athola
hype, and unnecessary framing. Includes termination and directness guidelines.
shared-patterns
athola
'Reference these patterns to validate consistency across the ecosystem.
release-notes-drafter
proflead
Draft release notes from changes and PRs. Use when a mid-level developer needs a structured changelog.
function-docstrings
proflead
Write concise docstrings for functions. Use when a junior developer needs help describing inputs, outputs, and errors.
planning-under-uncertainty
RefoundAI
Help users plan products and strategy when outcomes are unpredictable. Use when someone is dealing with ambiguous timelines, building in fast-moving markets, planning AI/ML projects, or asking how to make commitments when they don't know what will happen.
managing-up
RefoundAI
Help users work effectively with their manager and executives. Use when someone is struggling with their manager relationship, needs to influence leadership, wants to get better at executive communication, or is trying to build trust with their boss.
building-team-culture
RefoundAI
Help users build and maintain strong team culture. Use when someone is defining team values, creating psychological safety, onboarding to a new team, navigating cultural change, or building distributed team norms.
coaching-pms
RefoundAI
Help users develop and coach product managers. Use when someone is managing PMs, creating development plans, running performance reviews, or trying to level up their PM team's capabilities.
routine-logic-bugfixer
bex-co
Autonomous maintenance routine that picks one tricky logic unit in a
routine-logic-simplifier
bex-co
Autonomous maintenance routine that finds one convoluted unit of
stacks-logging
stacksjs
Use when implementing logging in Stacks - the log facade (info, error, warn, debug, success), dump/dd debugging, timing functions, file-based logging, or log configuration. Covers @stacksjs/logging and config/logging.ts.
single-or-array-pattern
EpicenterHQ
Pattern for functions that accept either a single item or an array. Use when creating CRUD operations, batch processing APIs, or factory functions that should flexibly handle one or many inputs.
error-handling
EpicenterHQ
Error handling patterns using wellcrafted trySync and tryAsync. Use when writing or reviewing try-catch blocks, refactoring try-catch to linear control flow, working with Result types, or returning HTTP error responses from route handlers.
control-flow
EpicenterHQ
Human-readable control flow patterns for early returns, guard clauses, and linearizing nested logic. Use when refactoring nested conditionals, replacing try-catch with linear flow, or restructuring decision logic.
qa-find-bugs-mcp
bex-co
Hunt bugs in the Beancount.io remote MCP server by driving the real POST /api-gateway/mcp endpoint with JSON-RPC and real MCP clients, checking transport, discovery, credential boundaries, tool and resource results, the result envelope and prompts against REST/GraphQL controls, reproducing failures, tracing root causes, and deduplicating findings. Use for MCP QA or an agent-endpoint bug hunt. Skip ordinary code review, bug implementation, browser, native-mobile, and CLI QA.