Discover development automation tools skills, compare source repositories and read the instructions for each workflow.
Submit complex code questions to OpenAI GPT-5 Pro for deep analysis when you have 20 minutes. Use when the user asks for architectural analysis, comprehensive code review, debugging complex issues, or requests...
Validates and registers command manifest files (YAML) to integrate new slash commands into Betty.
Spec-driven source translation & modernization workflow for codebases. Use when asked to migrate/translate a project (e.g., framework/SDK/language upgrade), or when the user wants a structured, externally-valid...
Best practices for branching, committing and creating pull requests in Git.
Use this skill when the user needs help formatting git commit messages according to Conventional Commits specification. Provides guidance on commit types, scope, and message structure.
View and analyze commits in GitHub repositories - commit history, diffs, and commit details using gh CLI
GitHub Actions workflow patterns for deployment. Use when creating CI/CD workflows.
Analyze and reorganize project file structures, identify dependencies, clean technical debt, and establish architectural patterns. Use when users need to: organize messy codebases, understand file dependencies...
Prepares applications for production by generating Dockerfiles, CI/CD pipelines, and platform configurations. Supports Docker, Vercel, Netlify, and GitHub Actions.
Deploy UK projects to Vercel using git-based workflow (never CLI deploy). Always London region (lhr1), dynamic version checking via Context7. Includes security headers and pre-deployment checklist. Triggers: de...
A high-level orchestration skill designed for end-to-end workflows, moving a project from a PRD to full Production deployment.
Automates Dockerfile optimization, multi-stage build configurations, and container security hardening.
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Expert guidance for software testing and quality assurance. Use when the user asks to write tests, create test plans, review code for bugs, perform code reviews, write test cases, set up testing frameworks, deb...
Safe, systematic approach to code refactoring with verification and rollback strategy.
Review implementation for code quality, style consistency, and best practices. Runs before security review. READ-ONLY - reports issues but does not fix them.
Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.
This skill should be used when the user asks to "review code", "check for bugs", "review my changes", "review this PR", "code review", or mentions reviewing code quality, security issues, or codebase fit. Launc...
Comprehensive guide for reviewing code to ensure it is clean, bug-free, and high-quality. Use when reviewing PRs, checking code quality, or before finalizing changes.
Enforces file naming conventions, directory structure, one class per file, Clean Architecture layer placement. Use when creating new files, organizing code, or refactoring file structure.
Expert code review for Java/Spring Boot and TypeScript/Next.js codebases. Performs multi-dimensional reviews covering correctness, security, testability, architecture, and maintainability. Automatically delegat...
Code quality enforcement with ESLint static analysis, VSCode workspace management, and automated code fixes. Supports JavaScript, TypeScript, React, Node.js with security and performance linting rules.
Handle code review feedback with technical rigor. Use this skill when receiving code review comments or feedback. Verify before implementing, ask before assuming, prioritize technical correctness over performat...
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, type...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.