systematic-debugging
Four-phase systematic debugging methodology for efficient problem resolution. Use when investigating bugs, errors, or unexpected behavior.
Essential command-line tools and system utilities.
Four-phase systematic debugging methodology for efficient problem resolution. Use when investigating bugs, errors, or unexpected behavior.
Coordinate multi-commit epic work using git worktrees, feature branches, PRs, and CI. Use when working on epics or large features that span multiple tasks.
User feedback patterns including success/error messages, loading states, confirmations, and progress indicators. Use when implementing notifications, toasts, or status updates. (project)
GitHub PR workflows including creation, review cycles, merge strategies, and stacked PRs. Use when creating PRs, reviewing code, merging branches, or managing stacked PR workflows. Covers rebase decision trees and AI-generated descriptions.
Update the project learning logs (PowerShell/cmd, Git/GitHub/Copilot, AWS, TypeScript, Next.js/React, Playwright) by merging new knowledge into existing categories across one or more files.
This skill should be used when the user asks to "create apex class", "write apex code", "implement service layer", "domain pattern", "selector pattern", "apex security", "bulkification", or mentions DRY, SOLID, or TDD principles for Apex. Provides framework-agnostic enterprise patterns for Apex development.
Implement advanced task features - Priorities, Tags, Due Dates, Reminders, Recurring Tasks, Search, Filter, and Sort. Use when adding Phase 5 advanced functionality. (project)
Invoke for complex multi-step tasks requiring intelligent planning and multi-agent coordination. Use when tasks need decomposition, dependency mapping, parallel/sequential/swarm/iterative execution strategies, or coordination of multiple specialized agents with quality gates and dynamic optimization.
Debug and investigate GitHub Actions workflow failures using gh CLI. Use when workflows are failing or when you need to understand CI/CD issues.
PROACTIVELY activates for ANY task with clear success criteria. This skill should be used when the user provides tasks like: "fix the bug", "add tests", "implement feature X", "refactor Y". Explicit triggers: "ralph this", "auto ralph", "loop it", "iterate". Auto-detects Ralph-suitable tasks (score >= 3/4): - Clear success criteria (tests pass, error gone, feature works) - Benefits from iteration (not one-shot) - Well-defined scope (specific files/functions) - Verifiable completion (can honestly output promise) Does NOT activate for: explanations, questions, vague requests. Output: Romanian. Input: Any (ro/en/ru/mixed).
Find and fix performance bottlenecks in ANY language or framework
Enterprise interactive survey orchestrator with AskUserQuestion tool integration, multi-select support, conditional branching, error recovery, and production-grade decision automation across all Alfred workflows; activates for requirement clarification, architectural decisions, risky operations, feature selection, and complex multi-step user interactions
Git workflow best practices and patterns. Use this skill when working with git operations, creating commits, managing branches, handling pull requests, or establishing team git workflows. Provides guidance on commit messages, branching strategies, and collaboration patterns.
Creates atomic git commits following Conventional Commits specification with detailed, well-structured messages. Analyzes changes and splits them into logical units. Use when committing code changes that need proper structure and comprehensive documentation (e.g., "commit my authentication changes" or "finished implementing search, time to commit").
Log key learnings to progress.txt during PRD iteration. Use when you discover codebase patterns, encounter gotchas, make important decisions, or learn something that would help future work sessions. Triggers on: log learning, add to progress, capture insight, record pattern, note gotcha, save lesson.
Quick code quality analysis that identifies common issues, anti-patterns, and improvement opportunities. Generates a concise summary report with actionable priorities. Use when the user asks to "analyze this code", "check code quality", "review this", or "what's wrong with this code".
Complete tp CLI reference for Linear integration. Use when working with Linear issues (create, update, comment, labels), managing parent/child relationships, or setting up team configuration. Covers both daily issue management and initial project setup.
Enables Claude to create, manage, and track tasks in Microsoft Planner via Playwright MCP
Use when working with Linear tickets/issues - establishes workflows for creating and updating tickets (issues)
Validate CasareRPA workflow JSON files for structural integrity, node dependencies, and connection validity. See schemas/ for JSON schema definitions. Use when: validating workflows, checking workflow JSON, testing workflow definitions, graph structure validation, node connections.
Generate background jobs for async tasks using Solid Queue. Use when user needs email sending, notifications, data processing, scheduled tasks, or says "send email in background", "process async", "create job", "schedule task", "queue work".