Loading...
Loading...
Found 334 Skills
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION.
Automatically generate intelligent PR descriptions by analyzing code changes. Uses Git diffs, commit history, and context to create comprehensive pull request descriptions with summary, changes, testing notes, and breaking changes.
Commit, push, and open a pull request in Azure DevOps. Use whenever the user wants to open, update, or draft a PR and the project is hosted on Azure DevOps (`dev.azure.com`, `visualstudio.com`, or explicit mentions of ADO, Azure Repos, or work item IDs like `AB#1234`). Links work items to the PR, sets reviewers, and supports draft-by-default.
git, git tags, pushing and pulling to repository. Any version control tasks.
Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Chinese Git Commit Skill. Analyze changes and generate Chinese conventional commit messages. Triggered when the user says "submit", "commit", "submit code", "submit changes", or "/commit-zh". Executed entirely by the main agent, no subagents used.
Preparar y ejecutar git commit con mensajes Conventional Commits inferidos del diff (tipo, scope, descripción, staging). Activar cuando el usuario pida hacer commit, generar el mensaje, separar cambios en varios commits, o use invocaciones tipo `/commit`.
Opens a pull request for a small jackin' change with the correct body shape and auto-selected verify-locally blocks. Use when the operator runs /jackin-dev:create-pr.
Create or update a PR from current branch to main, watch CI, and address feedback
Generates semantic commit messages following the Conventional Commits specification with proper types, scopes, breaking changes, and footers. Use when users request "write commit message", "conventional commit", "semantic commit", or "format commit".
Creates git commits. Use this skill whenever the user asks to commit, or whenever you need to commit changes as part of a task.