Total 50,402 skills, Version Control has 883 skills
Showing 12 of 883 skills
Utiliza esta habilidad para analizar cambios locales en el repositorio Git, redactar mensajes de commit profesionales en español y ejecutar commit/push de forma segura.
Analyzes changes since last release and updates CHANGELOG.md ONLY. Does NOT trigger releases.
Automate versioning and changelog generation using semantic versioning principles. Configure release automation, version bumping, and changelog tools. Use when implementing version management or automating release processes.
Create git commits with user approval and no Claude attribution
GitLab discussion operations via API. ALWAYS use this skill when user wants to: (1) view threaded discussions on MRs/issues, (2) create new discussion threads, (3) reply to discussions, (4) resolve/unresolve discussions.
GitLab search operations via API. ALWAYS use this skill when user wants to: (1) search across GitLab globally, (2) find issues/MRs/code/commits, (3) search within a group or project, (4) find users or projects by keyword.
Use when creating git commits in this project
Automatically creates semantic Git checkpoint commits during AI coding sessions. Replaces opaque platform checkpoints with transparent, queryable Git commits using Conventional Commits format with Git Trailers. You MUST follow this skill whenever you make code changes — commit after each meaningful edit.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Analyzes git diffs and commit history to intelligently fill PR templates and create pull requests via gh CLI. Use when user wants to create a PR, needs PR description help, or says 'create a pull request', 'fill PR template', 'make a PR', 'open a pull request', or mentions PR creation.
Create feature branches linked to issues with consistent naming conventions. Generates branch names from issue numbers and descriptions, creates the branch, and checks it out. Use when: create branch, new branch, feature branch, branch for issue, start working on issue, branch-create, /branch-create.
Automate Gitcode Pull Request creation workflow for OpenHarmony graphic subsystem including code commit, issue creation, and PR submission with proper template formatting. Use when user needs to create a PR for the Gitcode platform, especially for OpenHarmony graphic projects that require specific PR templates with CodeCheck tables and Signed-off-by tags.