Loading...
Loading...
Found 51 Skills
Create a PR title and draft description after substantive code changes are finished. Trigger when wrapping up a moderate-or-larger change (runtime code, tests, build config, docs with behavior impact) and you need the PR-ready summary block with change summary plus PR draft text.
Interact with GitLab repositories, merge requests, and APIs using the GITLAB_TOKEN environment variable. Use when working with code hosted on GitLab or managing GitLab resources.
This skill should be used when the user asks to "finish a hotfix", "merge hotfix branch", "complete hotfix", "git flow hotfix finish", or wants to finalize a hotfix and merge it into main and develop.
Use when starting task work that needs branch isolation, before planning or coding — creates a worktree branching from current remote main with freshness verification and project setup
Submit a kid-facing English content PR to the football-english repo (zxkane/football-english). Use this whenever the user asks to "submit this week's quiz", "publish a weekly quiz", "submit a daily reading", "add today's reading", "publish a daily article", "open a daily PR", "open a quiz PR", or hands over essay paragraphs (with optional KET/PET points, vocabulary, audio, image, questions) and expects them to land in the kid-facing site. The repo publishes two kinds of content — weekly quizzes (essay + 3-20 graded questions, one per ISO week) and daily readings (essay + TTS audio + image + structured KET/PET points + optional 0-3 small questions, irregular cadence). This skill picks the right shape, writes the JSON, validates it, and opens the PR end-to-end. Trigger this skill even if the user doesn't use the words "quiz", "daily", or "PR" — any handover of essay paragraphs intended for this repo qualifies.
The shared git layer every other skill borrows — where a worktree lives and what it's called, how to create/adopt/tear one down, which branch is the base, and whether to rebase or merge. Use when the user says "spin up a worktree for this", "make me a worktree", "where's the worktree for #42", "tear down this worktree", "clean up my worktrees", "what's the base branch here", "should I rebase or merge", or runs "/gitkit" — and whenever another skill needs any of those answers.
Use when the user asks to review a pull request — "review PR
Manages git worktrees including listing, creating, removing, and switching between worktrees. Use when the user mentions creating worktrees, create a work tree, create worktree, new worktrees, parallel branches, or working on multiple branches simultaneously. CRITICAL - PROACTIVE BRANCH PROTECTION - Before starting ANY development work (implementing features, fixing bugs, writing code, making changes), check the current branch. If on main/master branch, IMMEDIATELY suggest creating a feature branch worktree to prevent accidental commits to main. This is mandatory for all development requests.
Create GitHub pull requests with readiness checks, auto-drafted titles and descriptions, and remote push handling. Use when: create PR, pull request, open PR, submit PR, create pull request, PR for review, push and PR, pull-request, /pull-request.
OrchestKit skill directory. Use when you want to see available skills or need help.
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
Research-to-implement pipeline chaining 5 MCP tools with graceful degradation