Loading...
Loading...
Found 7,483 Skills
Research the codebase to answer questions. Search for relevant files, gather context, and provide clear answers.
Implement one task or scoped change: make the change, add valuable tests, and verify it works.
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the Task tool for architecturally enforced context isolation. Supports Jest, Vitest, pytest, Go test, cargo test, PHPUnit, and RSpec.
Stage changes, draft conventional commit messages, and commit with user confirmation. Use when user types /commit, asks to commit changes, or mentions creating a git commit.
Discover and use shared team skills stored in PostHog. Use when the user asks to list, browse, load, or manage "shared skills", "team skills", or references the "skills store" / "skill store".
Create Git commits with Conventional Commits analysis, safe staging, and concise message generation. Use when the user asks to commit changes or create a git commit.
Use prefered practices when using git. Use when Codex needs to perform actions with git or Github.
Submit or run an ML experiment on a compute environment (local, SLURM HPC, RunAI/Kubernetes). Use when the user wants to launch a training run, submit a job, run ablations, or execute an experiment script on any compute cluster.
[Hyper] Create one or more Conventional Commits from the current repository state. Inspect staged and unstaged changes, group them into logical change sets, generate a compliant message per group, and commit each group separately in sequence.
[Hyper] Analyze vague or relayed non-developer stakeholder requests (client, executive, PM, sales/support) by mapping them to codebase impact, presenting interpretation candidates with risks, then implementing only after confirmation. Use for stakeholder-message analysis, not browser QA testing, CI/build failures, or already-clear technical tasks.
Coordinate a full Paperclip release across engineering verification, npm, GitHub, smoke testing, and announcement follow-up. Use when leadership asks to ship a release, not merely to discuss versioning.
Git Worktree Manager