Skill UI

Runs external LLM CLIs (OpenAI Codex or Google Gemini) to review uncommitted changes, branch diffs, or specific commits, providing an independent second opinion before merges or releases.

A comprehensive guide to integrating Sentry into continuous integration and continuous deployment (CI/CD) pipelines (e.g., GitHub Actions, GitLab CI, CircleCI). This skill automates complex tasks such as creating releases, uploading source maps for readable stack traces, associating commits, and tracking deployment environments, ensuring rapid and accurate debugging of production errors.

Integrate Sentry into your CI/CD pipeline to achieve end-to-end release tracking. This skill guides you through using the Sentry CLI and SDK to record deployments, associate commits, upload source maps, and monitor crucial release health metrics. Key functions include detecting regressions, calculating crash-free session rates, and tracking user adoption curves for every deployed version.

This guide details how to use the Sentry CLI to manage the full application release lifecycle. Users can create versioned releases (using Semver or SHA), upload source maps to deminify stack traces, and associate specific git commits. This ensures that every error is accurately linked to the exact code version and deployment that caused it, significantly improving debugging and observability in CI/CD pipelines.

A comprehensive framework guiding feature planning and implementation through adaptive phases: Specify, Design, Tasks, and Execute. It enforces highly structured development practices by using EARS notation, atomic tasks, deterministic Conventional Commits, and mandatory code validation scripts. Features include requirement traceability, automatic verification, and a self-improving lessons layer, ensuring quality and compliance throughout the lifecycle.

This skill provides robust guidelines and patterns for managing environment variables and sensitive credentials securely. It is designed to ensure that secrets, API keys, and other confidential information are never accidentally exposed or logged in Claude sessions, terminal outputs, development logs, or version control commits (like Git). Use this skill when handling sensitive data in development workflows to maintain maximum security.

This skill automatically generates structured and user-friendly changelogs by analyzing the complete git commit history. It groups commits by time period (daily/weekly) and classifies changes into key categories (Features, Fixes, Docs, etc.), providing a concise summary of recent development activity for end-users. Ideal for answering 'what changed recently' or summarizing project updates.

This skill automates the entire software release workflow within Windsurf. It analyzes commit history based on conventional commits to determine the correct semantic version bump (major, minor, or patch). It then automatically generates comprehensive changelogs, manages Git tags, updates version files, and publishes the final release package to a registry. It is essential for teams implementing robust CI/CD practices.

This skill provides guidance for implementing tasks using structured workflow patterns, specifically following Conductor's TDD (Test-Driven Development) workflow. It helps manage phase checkpoints, organize git commits, and execute rigorous verification protocols. Use it when adhering to a defined development plan, ensuring quality gates are passed, and managing the entire lifecycle from initial planning to final validation.

A rigorous, security-focused code review process designed for Pull Requests (PRs), commits, and diffs. It moves beyond general reviews by focusing intensely on high-risk areas such as authentication, cryptography, external calls, and value transfer. The methodology is evidence-based, requiring detailed attack scenario modeling and generating comprehensive, auditable markdown reports to identify overlooked vulnerabilities and regressions.

This skill guides users on setting up automated code quality gates directly at the Git level. It covers best practices using frameworks like Husky, lint-staged, and pre-commit. Users can enforce linting, formatting, type-checking, and standardized commit message conventions (e.g., Conventional Commits) before code is committed or pushed, significantly improving code hygiene and development workflow consistency.

This command merges the results of the highest-ranked agent from a specified or latest session into the base branch. It automates the finalization of a development cycle by ensuring a clean and traceable history. Functionality includes merging the winner's branch, archiving all losing agents' commits using Git tags, and cleaning up temporary worktrees.