Branch promotes 4 control-plane command groups out of labs → make visible in root help.

Commands: org, project, repo, grant.

Changes:

labs.go — remove 4 groups from experimentalCommands list + --help hints.
root.go — flip 4 groups from Hidden (was "hidden during maturation") to visible.
org/project/repo.go — unhide command (drop Hidden: true).
grant.go — same unhide.
CLAUDE.md — doc update.

Net: these graduate from experimental to first-class visible commands. One commit 1d5cc0607.

Checked all docs. No stale labs references left behind.

Verified:

CLAUDE.md / AGENTS.md (symlink → CLAUDE.md) — 4 commands documented as full noun groups; labs section only lists tokens: profile. ✅
Command help strings (org/project/repo/grant .go) — no "experimental/labs/hidden/maturation" wording. ✅
README.md — never mentioned these commands. ✅ (nothing to update)
superpowers specs/plans — mention entire repo mirror as usage, no labs framing. ✅

Only remaining hits = CHANGELOG.md — historical release entries (entire labs review, blame/why labs, etc.). Those are past-tense records, correct to leave.

Branch is documentation-consistent. Nothing to fix.

Bottom line: strictly required — nothing. Recommended — one small README addition.

Why not much is needed:

entire agent-help renders live from the cobra tree — it's the documented source of truth, auto-picks up the now-visible commands. No edit needed.
entire <cmd> --help works; all 4 have solid Short/Long strings already.
CLAUDE.md already documents them as noun groups.

Where a gap exists:

README.md "Commands Reference" table (line 241) is the one human-facing curated list. It's a subset — already omits auth, api, dispatch, activity — so it's not exhaustive by design. But since org/project/repo/grant just became public control-plane commands, adding them keeps the table honest.

Recommendation: add 4 rows to that table. Small, matches existing style. Want me to?

Proposed rows:

Command	Description
`entire org`	Manage Entire organizations (create, list, get, delete)
`entire project`	Manage Entire projects (create, list, get, delete)
`entire repo`	Manage Entire repositories (create, list, get, delete, clone, mirror, visibility)
`entire grant`	Manage access grants and org membership (org, project, repo)

Say go, I add them.

Base directory for this skill: /Users/gtrrz-victor/.claude/skills/ship

Ship Changes

Commit current changes, push to remote, and update the PR.

Step 1: Analyze changes

Run git diff --stat and git diff to understand what changed
Run git status to see untracked files
Run git log --oneline -3 to match the repo's commit message style

Step 2: Commit

Stage only the relevant changed/untracked files by name (never git add -A or git add .)
Write a concise commit message that focuses on the "why" not the "what"
- If `` is provided, use it as the commit message
- Otherwise, draft one from the diff
Commit. If hooks fail, diagnose and fix — do NOT use --no-verify

Step 3: Push

Check if the branch tracks a remote: git rev-parse --abbrev-ref --symbolic-full-name @{u}
If not tracking, push with -u origin <branch>
If tracking, just git push
If push is rejected (remote has new commits), pull with rebase first then push

Step 4: Update PR

Find the open PR for the current branch: gh pr view --json number,body,title
If no PR exists, skip this step and inform the user
Compare the current PR body against the new changes:
- If the changes are within the existing PR scope, update the description to reflect the current state
- If the changes are additive or a follow-up, add a PR comment summarizing what was just pushed instead
When updating the PR body, preserve the overall structure but refresh the summary bullets and test plan
When adding a comment, keep it concise — bullet points of what changed and why
Before making any PR update (description edit or comment), show the user the exact text you plan to post and ask for their approval. Do NOT post until they confirm.

Rules

Never commit files that look like secrets (.env, credentials, tokens)
Never force push
Always show the user what was committed and the PR URL when done

2mo ago·41.1s

README change is within the PR's existing scope (docs for promoted commands). Proposed: tweak one bullet in the Changes section to mention the README. Exact edit:

Current bullet:

Docs & comments: updated the registration comments in root.go and documented the four groups in the CLAUDE.md / AGENTS.md command-layout section.

New bullet:

Docs & comments: updated the registration comments in root.go, documented the four groups in the CLAUDE.md / AGENTS.md command-layout section, and added them to the README Commands Reference table.

Rest of the body unchanged. Post this update?

Both Copilot comments handled.

Comment 1 — root.go (valid): Fixed in c6eb4a09f. Moved the 4 AddCommand calls into the Noun-groups block — they're noun groups, not standalone verbs. Replied.

Comment 2 — CLAUDE.md/AGENTS.md (wrong): Copilot missed the symlink. AGENTS.md -> CLAUDE.md, so editing CLAUDE.md updates both; PR desc is accurate. Replied explaining, no change.

Pushed. Build passes. lint:go has a pre-existing v1/v2 golangci-lint toolchain mismatch on your machine (not from this diff) — worth a separate fix if CI hits it, but CI likely runs the v2 binary.