Loading...
Loading...
Found 3 Skills
Set up a GitHub repo's metadata through the gh CLI: an inferred one-line About description + topics from the repo's own contents, and the issuekit lifecycle and priority labels. Use when the user says "repokit", "set the repo description", "add topics/tags", "write an About blurb for this repo", "provision the workflow labels", "set up this repo's labels", "add priority labels", or "configure this repo's metadata", meaning anything about a repo's About panel or its label vocabulary.
Own the GitHub issue lifecycle with five modes: create issues from a plan or description (kept independent for parallel worktree work), start a `ready` issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle and priority gaps. Use when the user says "create issues from this plan", "file an issue", "start issue #42", "close #42", "wrap up #42 now the PR merged", "sync my issues", "triage the backlog", "prioritize my issues", "set the priority on #42", "issuekit", or wants issues opened, started, landed, reconciled, ranked, or reviewed with the gh CLI.
(NS) Execute a GitLab issue end-to-end — status gates, worktree isolation, atomic delivery, MR, mandatory review+fix loop. Use for ISSUE_URL or "implement this GitLab issue". Not for local ad-hoc coding (ns-coder) or non-GitLab autonomous runs (ns-autonomous). Delegates coding to ns-autonomous; needs mcp-gitlab-usage + ns-reviewer.