Essential command-line tools and system utilities.
Convex Components - Presence, ProseMirror/BlockNote collaborative editing, and Resend email integration. Use when working with presence, prosemirror, blocknote, resend, email, collaborative editing, facepile, convex.config.ts, defineApp, or @convex-dev components.
Create or update project issues following the Epic specification format with Behaviors (Rules + Examples), Technical Specifications (Action/Hook/Component/Service), and task lists. Use when user asks to create/update an issue, document requirements, or write specifications for a new feature.
Debug and fix task-related issues in STEEB app. This skill should be used when encountering task creation, completion, deletion, or state management problems in the STEEB task management system.
Track GitHub milestone progress and issue completion. Use when user asks about milestone status, how many issues done, sprint progress, or completion percentage.
Comprehensive change tracking and audit logging system that monitors file modifications, code changes, and project evolution. Use when tracking project history, maintaining audit trails, analyzing development patterns, or when detailed change documentation is required for compliance and team collaboration.. Enhanced with Context7 MCP for up-to-date documentation.
This skill creates pull requests using the GitHub CLI with AI-generated descriptions. It analyzes the current branch, detects available target branches, and generates concise PR descriptions based on the commit history and changes. Use this when asked to create a pull request, file a PR, or when the user uses the `/pr` or `/gpr` command. It automates the PR creation process while ensuring quality descriptions.
Code refactoring analysis for code smells, decomposition, and modernization using PAL MCP. Use for cleanup, technical debt reduction, or code organization. Triggers on refactoring requests, code smell detection, or cleanup tasks.
Creates a streamlined pull request from v2 (staging) to main (production) with change summary, affected apps detection, and deployment checklist. This skill should be used when ready to deploy staging changes to production, creating a production PR, or promoting v2 branch to main.
Specialized agent for creating, maintaining, and organizing comprehensive documentation for the BarqNet project. Records all changes, creates technical specifications, API documentation, user guides, deployment guides, and maintains documentation consistency across the entire codebase. Use when documenting features, creating guides, or organizing project knowledge.
Four-phase root cause analysis process to find bugs 10x faster
Programmatic Zellij terminal workspace management for agentic workflows. Use when orchestrating parallel development tasks, creating tabs/panes, tracking developer intent, or managing terminal layouts. Triggers include: (1) Creating tabs with specific naming conventions, (2) Spawning multiple panes for parallel work, (3) Logging and retrieving developer intent/context, (4) Workspace layout organization for agent coordination, (5) Integration with iMi worktrees for branch-per-pane workflows.
Provides critical feedback and alternative architectural perspectives on code changes. Use when you want to explore different ways to implement a feature or find potential flaws in the current plan.
Design and implement n8n workflow automations with best practices
Guidelines for writing reports, organizing files, and generating code artifacts
Task-driven development workflow with TODO tracking. Use when user says "dev", "dev-workflow", or asks to work on tasks, develop features, or proceed with implementation.
Generate semantic commit messages in English. Use when the user asks for a commit message or semantic commit guidance. Prefer the user’s stated change intent and context, and keep the message consistent with the actual change.
Use for GitHub operations - creating PRs, checking CI status, reviewing PR comments, managing issues.
Design and build n8n workflows - triggers, nodes, flow logic, error handling, and best practices
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
Guidance for responding through Slack MCP: immediate acknowledgements, progress cadence, thread discipline, message templates, and failure handling. Use whenever Codex must reply to Slack mentions or share progress/results.
