Loading...
Loading...
Found 9,399 Skills
(NS) Sync existing GitLab issues with local planning and execution — milestone, RF labels, status transitions, assignee, estimates, spent time. Use during implementation when tasks link to GitLab issues or after plan-version-from-gitlab sync — not for creating new issues (use mcp-gitlab-usage). Always use atomic set_issue_labels and three-step status cycle. Read mcp-gitlab-usage for tool contracts.
(NS) Ad-hoc coding worker — bug fixes, small refactors, scripts, migrations — without full SDD. Entry priority 5: use for "just implement this", "quick fix", or concrete coding without execution-handoff (also C2 under ns-code-autonomous). Do NOT use for GitLab ISSUE_URL (ns-execution-gitlab-issue), multi-day/version scope (ns-spec-driven), diagnosis-only (ns-code-investigator), or when execution-handoff.md exists. Do NOT generate requirements/tasks/handoff.
(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).
(NS) Generate or refresh lean architecture-rules.md for AI agents — stack, layout, patterns, constraints. Use when the user asks for architecture rules, .nextstage-harness/rules/architecture-rules.md, agent conventions, or "document how this repo works for the AI". Do NOT use for business specs (ns-harness-codebase-reverse-spec), brownfield maps (ns-harness-bootstrap-brownfield), or one-off Cursor rules without a full architecture pass.
(NS) Full post-harness-init bootstrap in one session — architecture rules, sync, brownfield map, reverse business spec, project AGENTS.md. Use for "harness prepare", post-install setup, onboard brownfield, or running all prepare skills without separate slash commands. Do NOT use for greenfield with no app code, single-skill runs, or CLI-only baseline AGENTS.md.
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Recreates or builds UI designs in Sketch from a reference URL, screenshot, or source code with side-by-side screenshot fidelity validation using Sketch MCP (`get_document_info`, `get_layer_tree_summary`, `get_screenshot`, `get_design_assets`, `get_symbol_overrides`, targeted `run_code`). Use when the user wants to design, mock up, or reproduce a page or screen in Sketch from the web, an image, or code.
Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week"
Use when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "is there a template for", and "how did we do this last time"
Full pull-request review — fetch the PR, run the project's validation, review the diff with fresh eyes (dispatching the code-reviewer agent), categorize issues by severity, post the review to GitHub (approve / request-changes / comment), and save a report. The agentic gate that runs on an open PR before a human approves. Use after piv-create-pr.
Push the current feature branch and open a pull request, ready for review. Use after a ticket's implementation is committed on its own branch — it detects the base branch, pushes, opens the PR with a clear body (summary · what changed · validation status), and returns the URL to hand to a reviewer.
Creates a new git commit for all uncommitted changes with an atomic, conventionally-tagged message. Use when work is complete and ready to be committed.