changelog-gen
Crea automáticamente changelogs orientados al usuario a partir de commits de git. Analiza el historial, categoriza los cambios y transforma commits técnicos en notas de release claras y amigables para el client...
Discover business git workflows skills, compare source repositories and read the instructions for each workflow.
Crea automáticamente changelogs orientados al usuario a partir de commits de git. Analiza el historial, categoriza los cambios y transforma commits técnicos en notas de release claras y amigables para el client...
BOOTSTRAP PROTOCOL: Initialize session with recent git activity, user task context, and relevant architectural decisions. Run this at the start of every coding session.
Audit code compliance with AGENTS.md project guidelines. Checks adherence to project conventions, naming, patterns, and standards. Read-only analysis. Use before PR. Triggers: review agents.md adherence, check...
Orchestrate fixing issues found by $review. Handles issue discovery, user confirmation, plan creation, and execution via $implement. Triggers: fix review issues, fix findings, address review feedback.
Context-gathering for finding files to read. Maps codebase structure, returns overview + prioritized file list with line ranges. Thoroughness: quick for lookups, medium for bugs/features, thorough for multi-are...
Use when writing Pull Request titles or commit messages to follow the Korean action word convention.
Generate conventional commit messages following best practices. Use when creating structured git commit messages.
Guide Git workflows including branching, merging, rebasing, and conflict resolution. Use when managing Git operations or resolving complex Git scenarios.
Manage Azure Repos including branches, pull requests, and code reviews. Use when working with Azure Repos or managing repository operations.
Generate comprehensive changelogs from git history following Keep a Changelog format. Use when creating release notes or maintaining version history.
Generate CI/CD pipeline configurations for GitHub Actions, GitLab CI, Jenkins. Use when setting up automated build and deployment pipelines.
Automated code review with security, performance, and best practices analysis. Use when reviewing pull requests or analyzing code for vulnerabilities, performance issues, or maintainability concerns.
Generate comprehensive pull request descriptions with summaries and test plans. Use when creating PR descriptions or documenting code changes.
Guide for creating and maintaining repository-local CLAUDE.md files that capture project-specific context, patterns, and conventions. Use when initializing repositories for Claude Code, updating project memory,...
Guideline for creating multiple commits.
Rule for creating PR (pull request) description
GitHub PR creation workflow with automated code review. Use when user wants to create a PR, requests `/pr`, or needs to push changes to GitHub with quality checks.
Generates properly formatted commit messages following project conventions. Use when creating commits or when users need help writing commit messages. Inspects staged changes and creates messages with component...
Use when asked to "review code", "review PR", "review diff", "check this PR", "do a code review", or mentions "code review", "PR review", "full diff", "cross-file patterns", "code quality", "review changes".
Railway deployment, CI/CD workflows, GitHub Actions, and smoke tests. Handles Railway configuration, GitHub Actions workflows, deployment automation, and health checks. Use when working with deployment, CI conf...
Address PR feedback with iterative refinement. MUST BE USED when fixing PR issues. Supports auto-detection (CI failures, code review) and manual triage (user reports bugs). Creates Beads issues for all problems...
Assist in writing or updating plan documentation for the FundViewGit reskin
Creates git branches with proper naming. Use when creating branches, starting new work, or switching to feature branches.
Generates commit messages and creates commits. Use when writing commit messages, committing changes, or reviewing staged changes.
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.