Loading...
Loading...
Found 74 Skills
Create a traceable Git branch for the current task.
Create a pull request in a mitodl GitHub repository using the org's standard PR template. Triggered by /olpr or whenever the user asks to open a pull request in a repo whose remote is under the mitodl GitHub organization. Guides branch inspection, title/body population, and gh pr create invocation.
Usar al pedir implementar, desarrollar o ejecutar trabajo referenciado por una historia de usuario o tarea. Solo debe usarse si la historia o tarea se encuentra en estado `Ready`. Activar tambien cuando el usuario mencione "ejecutar tareas", "codificar", "desarrollar la US", "trabajar en el TK" o cualquier variante que implique escribir codigo para una historia o tarea ya especificada.
Use when ALL tasks in an epic or branch are closed and you are ready to integrate the entire body of work - never after individual task completions, never mid-epic
Use when the user wants to verify their understanding of a branch's code changes by being quizzed on runtime behavior, assumptions, failure points, and edge cases instead of just reading diffs
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Use when merging a branch to main without touching the primary worktree directly, when /ship or /reflect needs to integrate work, or when autonomous mode blocks direct main commits
Push branch and create GitHub pull request. Use when the user wants to open a PR, submit changes for review, or push and create a pull request.
Guide for working in parallel with other agents. Use when another agent is already working in the same directory, or when you need to work on multiple features simultaneously. Covers git worktrees as the recommended approach.
Linear ticket lifecycle for any project. Use when starting work on a Linear issue, ending work on an issue, or asking what to work on next. Triggers: start KAT-N, pick up, implement, finish, complete, done with, close, what's next, next ticket, next issue. Handles blocker validation, status transitions, context loading, branch creation, evidence gating, and chain promotion.
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.
Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating.