Debugging
Find and fix bugs, error analysis
ring:dev-frontend-e2e
by LerianStudio
Gate 5 of frontend development cycle - ensures all user flows from product-designer have passing E2E tests with Playwright across browsers.
ring:systematic-debugging
by LerianStudio
Four-phase debugging framework - root cause investigation, pattern analysis, hypothesis testing, implementation. Ensures understanding before attempting fixes.
ring:defense-in-depth
by LerianStudio
Multi-layer validation pattern - validates data at EVERY layer it passes through to make bugs structurally impossible, not just caught.
ring:dev-validation
by LerianStudio
Development cycle validation gate (Gate 5) - validates all acceptance criteria are met and requires explicit user approval before completion.
ring:test-driven-development
by LerianStudio
RED-GREEN-REFACTOR implementation methodology - write failing test first, minimal implementation to pass, then refactor. Ensures tests verify behavior.
ring:linting-codebase
by LerianStudio
Parallel lint fixing pattern - runs lint checks, groups issues into independent streams, and dispatches AI agents to fix all issues until the codebase is clean.
ring:root-cause-tracing
by LerianStudio
Backward call-chain tracing - systematically trace bugs from error location back through call stack to original trigger. Adds instrumentation when needed.
ring:condition-based-waiting
by LerianStudio
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.
ring:dispatching-parallel-agents
by LerianStudio
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
ring:production-readiness-audit
by LerianStudio
Comprehensive Ring-standards-aligned 44-dimension production readiness audit. Detects project stack, loads Ring standards via WebFetch, and runs in batches of 10 explorers appending incrementally to a single report file. Categories - Structure (pagination, errors, routes, bootstrap, runtime, core deps, naming, domain modeling, nil-safety, api-versioning, resource-leaks), Security (auth, IDOR, SQL, validation, secret-scanning, data-encryption, multi-tenant, rate-limiting, cors), Operations (telemetry, health, config, connections, logging, resilience, graceful-degradation), Quality (idempotency, docs, debt, testing, dependencies, performance, concurrency, migrations, linting, caching), Infrastructure (containers, hardening, cicd, async, makefile, license). Produces scored report (0-430, max 440 with multi-tenant) with severity ratings and standards cross-reference.
debugging-patterns
by romiluz13
"Internal skill. Use cc10x-router for all development tasks."
pr-review
by jellydn
Fix PR review comments by implementing requested changes
report-issue
by codemie-ai
This skill should be used when the user wants to report a bug, file an issue, or suggest a feature for the CodeMie Code CLI tool (codemie-ai/codemie-code repository on GitHub). Trigger phrases include: "report a bug", "open an issue", "submit an issue", "file a bug report", "something is broken in CodeMie", "report to GitHub", "create a GitHub issue", "suggest a feature for CodeMie", "request an enhancement", "I have a feature idea", "codemie is not working", or any mention of filing a report for CodeMie. This skill automatically collects diagnostic context (OS, Node.js, CLI version, installed agents, active profile, codemie doctor output, recent debug logs) and creates a structured GitHub issue via gh issue create with a user-confirmed preview step before submission.
e2e
by NeverSight
Run e2e tests, fix flake and outdated tests, identify bugs against spec. Use when running e2e tests, debugging test failures, or fixing flaky tests. Never changes source code logic or API without spec backing.
linear-list
by Finesssee
List and get Linear issues. Use when viewing issues, checking status, or fetching issue details.
linear-update
by Finesssee
Update Linear issues. Use when changing status, priority, assignee, or labels.
linear-create
by Finesssee
Create Linear issues. Use when creating bugs, tasks, or feature requests.
swe
by knoopx
Applies software engineering best practices, design principles, and avoids common anti-patterns. Use when designing systems, reviewing code quality, refactoring legacy code, making architectural decisions, or improving maintainability.
writing
by iliaal
Prose editing, rewriting, and humanizing text for natural tone. Use when asked to "write", "rewrite", "edit", "humanize", "improve text", "fix the tone", "remove AI language", "proofread", or when writing copy, docs, blog posts, articles, emails, PR descriptions, or plans.
generic-feature-developer
by travisjneuman
Guide feature development with architecture patterns for any tech stack. Covers frontend, backend, full-stack, and automation projects. Use when adding new features, modifying systems, or planning changes.
debugging-dbt-errors
by AltimateAI
Debugs and fixes dbt errors systematically. Use when working with dbt errors for: (1) Task mentions "fix", "error", "broken", "failing", "debug", "wrong", or "not working" (2) Compilation Error, Database Error, or test failures occur (3) Model produces incorrect output or unexpected results (4) Need to troubleshoot why a dbt command failed Reads full error, checks upstream first, runs dbt build (not just compile) to verify fix.
optimizing-query-text
by AltimateAI
Optimizes Snowflake SQL query performance from provided query text. Use when optimizing Snowflake SQL for: (1) User provides or pastes a SQL query and asks to optimize, tune, or improve it (2) Task mentions "slow query", "make faster", "improve performance", "optimize SQL", or "query tuning" (3) Reviewing SQL for performance anti-patterns (function on filter column, implicit joins, etc.) (4) User asks why a query is slow or how to speed it up
operational-risk
by JoelLewis
"Operational risk management: trade breaks, settlement fails, error handling, loss event taxonomy, key risk indicators, incident management, and business continuity for trading operations."
order-lifecycle
by JoelLewis
"Order lifecycle management: order states, FIX protocol basics, order types, time-in-force, cancel/replace workflows, order validation, and state machine design for trading systems."