ns-execution-gitlab-issue
Installation
SKILL.md
Execute GitLab Issue
Entry priority 1 for external GitLab ISSUE_URL. SDD unit mode (below) when delivery-units.md supplies unit + issue_iid — not an external URL. Full routing: ../../ns-harness/references/code-skill-routing.md.
Routing (read first)
Entry priority 1. Harness table: ../../ns-harness/references/code-skill-routing.md. Trigger phrases: references/entry-triggers.md.
| Handoff | Target |
|---|---|
| Phase 2 execution (external, single unit) | coder-agent → ns-coder in existing worktree — skip ns-autonomous (planning-decision.md single-unit; spawn gate) |
| Phase 2 execution (external, multi-unit) | ns-autonomous (Engine mode) |
| Phase 2 execution (SDD unit) | ../../ns-coder/references/run-implementation.md (unit tasks only) |
| MR / status / time / comments | mcp-gitlab-usage |
| Phase 4 review gate | reviewer-agent → ns-reviewer; then ns-judge in-session only if Code Review: Approved |
| Rejected fix loop (external, single unit) | coder-agent / ns-coder (same worktree; no A) |
| Rejected fix loop (external, multi-unit) | ns-autonomous → C2 (same worktree; no re-entry to this skill from A/C2) |
| Rejected fix loop (SDD unit) | coder-agent → ns-coder / run-implementation (same worktree; no ns-autonomous) |