Loading...
Loading...
Found 47 Skills
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 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.
Quick status check for current branch and PR state showing local changes, CI results, reviews, and merge readiness. Use when user wants branch status, PR state, CI check results, review status, or merge readiness. Use for "pr status", "what's the status", "is my PR ready", "check CI". Do NOT use for creating PRs, pushing changes, or fixing review comments.
Git worktree management with safe defaults and flexible placement strategies. Use when users ask to: (1) create a new worktree or work on multiple branches in parallel, (2) list existing worktrees, (3) remove or clean up worktrees, (4) manage worktree placement (subfolder vs sibling directory), or any other git worktree operations.
Implements an approved spec. Validates that the state means "Approved" (in any language), creates a git branch named after the spec, switches to it, and starts the implementation step by step with pauses to review diffs.
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
Autonomous experiment loop for optimization research. Use when the user wants to: - Optimize a metric through systematic experimentation (ML training loss, test speed, bundle size, build time, etc.) - Run an automated research loop: try an idea, measure it, keep improvements, revert regressions, repeat - Set up autoresearch for any codebase with a measurable optimization target Implements the autoresearch pattern with MAD-based confidence scoring, git branch isolation, and structured experiment logging.
Sync the local main branch with the latest code from the official upstream or origin remote
Generate a pull request subject line and a concise description by analyzing the commits and diff on the current local git branch. Use this whenever the user is preparing a PR and wants help writing its title or body — phrases like "write a PR description", "summarize my changes for a PR", "what should the PR title be", "draft the PR for this branch", or "describe these commits". Trigger even if the user doesn't say the exact words "pull request" but is clearly wrapping up branch work and wants it summarized for review. This skill only reads git locally and prints the result for the user to copy — it never pushes or edits anything on GitHub.
DubStack CLI reference. Use for managing stacked changes (git branches). Covers creating stacks, navigating, submitting PRs, rebasing (restacking), and undoing mistakes.
Create a new Git branch or code worktree for experiments, features, baselines, rebuttal fixes, or method revisions. Use when starting an isolated code direction, creating a branch, creating a project-aware code worktree under a project control root, or setting up a worktree with UV sync, IDE config copying, linked assets, and worktree memory.