Loading...
Loading...
Found 4,154 Skills
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Execute Tests - walks through test cases from the test plan, collects results, and updates the plan. Use when verifying a feature implementation.
(NS) Orchestrate partitioned version implementation slice-by-slice — one subagent per slice, commit, auto-advance until done or stop. Use when version-roadmap.md has pending slices and the user asks to orchestrate/execute all slices. Do NOT use for non-partitioned versions, ad-hoc coding (ns-code-coder), or partitioning itself (ns-sdd-version-partitioner).
Autonomously develops a complete feature from priming through planning, execution, and commit by chaining the four core PIV-loop skills. Use when you want a full hands-off feature build from a single description.
Operator-invoked review of the full branch (every commit vs. the base branch) plus any uncommitted local changes before opening or updating a PR. Strict gatekeeper stance with per-diff and branch-level checks. Language-agnostic.
Use before commit or review when the operator wants to quickly understand the current staged, unstaged, untracked, branch, or PR diff without reading a long audit.
Use after an AI coding session or before commit, PR, handoff, or release when the operator wants a human-readable summary of what was done and why, with key files and current state, without a long audit.
Commit, push, and create a draft PR using the pr-description format, with UX flow context when relevant.
Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
Despliega local o en Railway y da de alta el webhook contra el proveedor que elegiste.
This skill should be used when the user asks to "rotate SSH keys", "regenerate SSH keys", "replace SSH keys", "renew SSH keys", or when the agent needs SSH access to a deployed VM for troubleshooting (logs, debugging, database access) but discovers the expected SSH key file is missing from the local disk (e.g. `~/.ssh/<repo-name>` does not exist). Also use when the user mentions "lost SSH key", "SSH key not found", "can't SSH into server", "permission denied SSH", "moved to a new computer", or "cloned repo on another machine".
Execute an implementation plan through to a verified, committed code change. Use after `plan-implementation` produces the ordered `Stages` plan.