Loading...
Loading...
Found 696 Skills
Automate Git workflows with atomic commits, Beads integration, and real-time sync. Use when managing Git commits, branches, task tracking, or handling complex multi-file changes with proper validation.
Request code review and route results to a tmux pane. Default flow commits first; optional opt-in flow can target an existing commit without commit/push.
Fetches and classifies PR review feedback with context isolation. Returns structured JSON with thread IDs for deterministic resolution. Use when analyzing PR comments before addressing them.
Update dependencies safely — check changelogs, run tests, create PR
Update the current local work branch by merging the latest base/default branch with pure git and no automatic push. Use when the user invokes `/update-branch`, says "update branch", or asks to merge the latest base branch or default branch into this branch.
AntiGravity Start Work/Finish Work/New Project Initialization Process. Loaded when saying 'Start Work', 'Finish Work', or 'Initialize Project'.
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`.
Use when generating or updating the changelog, preparing release notes, or populating the Unreleased section of CHANGELOG.md for the jackin project
Create an exercise directory structure containing section, problem, solution, and explainer that passes lint checks. Use this when users want to build an exercise framework, create exercise templates, or set up new course chapters.
Push projects to GitHub with three automatically determined modes: **First-time Push** (large file scanning → generate .gitignore → git init → create repo via gh → push), **Daily Update** (commit + push), **Version Release** (tag + create Release, optional attached download files). Core principle: Safety First: Must scan for large files and sensitive files before pushing, better to ask one more question than push something that shouldn't be pushed. Triggered when users say "push to GitHub", "git push", "upload to GitHub", "commit and push", "release version", "create release", "create tag", "/git-push". Not applicable for: Planning which features go into which version number (use issue-pool—this skill only handles tagging pre-determined version numbers), complex git operations like rebase/cherry-pick/resolving conflicts/modifying history/rolling back (use git commands directly, this skill does not cover these), self-testing and acceptance before code is completed.
This skill should be used as a mandatory final sanity check before git commit, PR creation, or declaring work done. Triggers on "commit", "push", "PR", "pull request", "done", "finished", "complete", "ship", "deploy", "ready to merge". Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.
Only use when the user explicitly invokes this skill by name.