Skill UI

This powerful skill manages Git worktrees to enable safe, isolated parallel feature development. It standardizes branch isolation, automatically allocates unique network ports, and synchronizes environments, allowing multiple agents or terminal sessions to work on different branches simultaneously without conflicts. It also provides mechanisms for detecting and safely cleaning up stale worktrees.

Creates isolated git worktrees with prioritized directory discovery, ignore verification, dependency bootstrapping, and clean baseline tests so feature branches launch safely alongside ongoing work.

This tool provides comprehensive automation for core GitLab operations, streamlining the entire development lifecycle. Users can manage projects, track issues, review merge requests, manage branches, and monitor CI/CD pipelines. It leverages a unified API interface to handle complex workflows, ensuring efficiency in version control and collaborative development environments.

This guide details the best practices for utilizing a code review sub-agent. It should be used after completing tasks, implementing major features, or before merging code into main branches. The process ensures that work results are validated against requirements, allowing reviewers to focus purely on the output rather than the development history, thus catching issues early.

This comprehensive guide details how to set up robust Continuous Integration/Continuous Deployment (CI/CD) pipelines for HubSpot integrations using GitHub Actions. It covers unit tests, deep integration tests against a developer test account, and secure secret management. Ideal for automating HubSpot API testing, ensuring consistent code quality across branches, and implementing reliable deployment workflows for CRM features.

A comprehensive guide to setting up CI/CD pipelines for ElevenLabs integrations. It implements a robust two-tier testing strategy: running mocked unit tests on every push to save API quota, and executing gated, real integration tests only on main branches or manually. Essential for automated validation of TTS projects using GitHub Actions.

This skill analyzes the comprehensive commit history between two branches to generate a concise, objective, and highly structured Pull Request (PR) description. It automatically groups changes by domain, summarizing the purpose, technical notes, and user impact, ensuring consistency and minimizing manual documentation effort.

This guide establishes the Conventional Branch specification for naming Git branches. It defines standardized prefixes (e.g., feature/, bugfix/, hotfix/) and enforces strict rules (lowercase, kebab-case, no underscores) to ensure consistency across development teams. Use it to validate, create, or understand the correct naming structure for any new branch, improving project traceability and collaboration.