Script and automate repetitive tasks and workflows.
Expert in migrating monolithic, legacy systems to modern architectures using patterns like Strangler Fig, CDC, and Anti-Corruption Layers. Use when modernizing legacy codebases, breaking monoliths, or planning incremental migrations. Triggers include "legacy migration", "modernization", "strangler fig", "monolith to microservices", "legacy rewrite", "incremental migration".
Use for code review and quality feedback from both Codex and Gemini. Triggers on "council review code", "council code review", "have council review this", "get council feedback on code".
ALWAYS apply this skill for ANY software development task. Triggers: implement, create, build, add, write, code, function, class, component, API, feature, fix, bug, debug, refactor, improve, clean, review, check, design, architect, structure, test, endpoint, module, service, handler, controller, model, schema, migration, deploy, configure. This skill enforces kadoppe's development principles for all coding work.
Generate comprehensive pull request descriptions with summaries and test plans. Use when creating PR descriptions or documenting code changes.
Guidelines for writing reports, organizing files, and generating code artifacts
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.
Git best practices, branching strategies, commit conventions, and PR workflows. Use when reviewing git history, writing commits, setting up branching strategy, or improving git practices. Triggers on "git best practices", "commit message", "branching strategy", or "PR workflow".
Reviews Advent of Code TypeScript solutions for code quality, TypeScript idioms, and performance. Use when asked to review a day's solution, critique AoC code, or get feedback on puzzle implementations.
Spec-Driven Development (SDD) agent for maintaining synchronized specifications, code, and documentation. Core principle: "1 Todo = 1 Commit = 1 Spec Update". Use this skill when: - Starting a new feature or task that needs specification - Implementing code based on existing specifications - Validating that code matches specifications - Updating CHANGELOG.md with changes - Managing PRD/specification documents - Ensuring traceability between requirements and implementation Triggers: "spec", "specification", "PRD", "requirements", "SDD", "spec-driven"
Generate comprehensive technical specifications from GitHub Pull Requests. Use when users provide a GitHub PR URL and request documentation, technical specs, or change analysis. Analyzes PR commits and diffs using gh CLI and git commands to produce structured documentation covering folder structure, DB schema changes, API definitions, test changes, and dependency updates.
This skill should be used when the user asks to "run tasks in parallel", "create worktrees", "dispatch parallel agents", "orchestrate execution", or when autonomous-dev needs to execute independent tasks simultaneously. Manages git worktrees for isolated parallel development.
Guide for creating commit message. This skill should be used when you try to create a commit message.
Multi-language SOLID detection rules. Project type detection, interface locations, file size limits per language.
Git convention for branch naming, commit messages, and issue labels based on GitFlow and Conventional Commits. Use when creating branches, writing commit messages, or setting up issue labels.
Follow consistent project structure, version control practices, environment configuration, code review processes, and development conventions across the entire application. Use this skill when organizing project files and directories, when writing commit messages or creating pull requests, when managing environment variables and configuration, when participating in code reviews, when defining testing requirements, when using feature flags, when maintaining changelogs, when documenting setup instructions, or when establishing consistent development practices across the team.
Analyze staged files, group by category, and generate conventional commit specs as JSON.
Analyze GitHub repositories to extract insights about commit frequency, outstanding contributors, release timeline, and project health metrics. Use when users request repository analysis, commit history investigation, contributor identification, release tracking, or development activity assessment for any GitHub project.
Intelligent git commit assistant that analyzes staged and unstaged changes in the current working directory, generates commit messages following Conventional Commits specification (conventionalcommits.org), and executes commits after user approval. Use when the user asks to create a commit, wants help writing a commit message, or says "commit these changes" or similar requests.
Inspect GitHub PR checks with gh, pull failing GitHub Actions logs, summarize failure context, then create a fix plan and implement after user approval. Use when a user asks to debug or fix failing PR CI/CD checks on GitHub Actions and wants a plan + code changes; for external checks (e.g., Buildkite), only report the details URL and mark them out of scope.
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").
Creates well-formatted conventional commit messages from your git changes. Analyzes git diff and status to generate proper commit messages following conventional commits format. Use when the user wants to commit changes or needs help writing commit messages.
