gitlab-wiki-bootstraplisted

Bootstrap or extend a team-facing GitLab Wiki for a project — explores the actual codebase (not generic boilerplate) to populate Home plus type-specific pages (PrestaShop: Modules/Theme/Local Development/Gotchas; Laravel: Integrations/Jobs & Queues/Deployment/Testing/Gotchas). Wiki upkeep afterwards is a PERSONAL habit (see Step 5) — never written into the project's own CLAUDE.md/AGENTS.md, since that would force every teammate's agent to depend on `glab` CLI just from touching the repo. Works both for brand-new projects with no wiki AND for established projects with months/years of history — for the latter, audits what already exists (wiki pages, README, docs/, CLAUDE.md) first and extends/corrects rather than starting from a blank slate. Use when the user says "monta la wiki", "crea la wiki para X", "documenta este proyecto en GitLab", "actualiza/completa la wiki de X", or wants team documentation set up or brought up to date for any project regardless of its age. Distinct from a personal notes/second-brain
educlopez/mallard · ★ 3 · Code & Development · score 72

Install: claude install-skill educlopez/mallard

# GitLab Wiki Bootstrap Sets up (or extends) a real, populated GitLab Wiki — not an empty shell. The value is in exploring the actual codebase for concrete detail (real module names, real integration behavior, real gotchas), the same way you'd explain the project to a new teammate. Generic boilerplate pages are worse than no wiki at all — don't ship those. Works for two starting points: - **Brand-new project, no wiki** — Steps 0 → 2 → 3 → 4, straightforward. - **Established project, possibly with history/existing docs/existing wiki pages** — add Step 1 (audit) before writing anything. Don't treat this as a from-scratch bootstrap: mine what's already there first. ## Step 0 — check prerequisites ```bash glab auth status ``` Get the project's numeric ID (needed for all wiki API calls): ```bash glab api "projects/<group%2Fsubgroup%2Fproject>" | jq .id ``` Check the Wiki feature is enabled (it usually is by default): ```bash glab api "projects/<id>" | jq .wiki_access_level ``` If `disabled`, enable it: ```bash glab api -X PUT projects/<id> -f "wiki_access_level=enabled" ``` ## Step 1 — audit existing state (skip only for a truly brand-new project) An "existing project" here means: any repo with real commit history, even if it has never had a wiki. Don't assume empty — check: 1. **Existing wiki pages**: ```bash glab api "projects/<id>/wikis" | jq -r '.[].slug' ``` If any exist, `glab api "projects/<id>/wikis/<slug>"` each one and read the content. Note w