[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F56NPQ218MPG4SWQZ44XFX":3,"skill-same:01M7F56NPQ218MPG4SWQZ44XFX":43},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M7F56NPQ218MPG4SWQZ44XFX","forge-gitlab",null,"How each step of the workflow skill is done on GitLab with glab — Issues, merge requests, Closes #n, scoped labels and the one-call status swap GitLab Free needs, the closing-word trap, Draft merge requests, milestones and the board. Activate with the workflow skill whenever it sends you to the forge.","workflowaiorg\u002Fworkflow","workflowaiorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F344728430?v=4","01M7F5606QN4BXN2KJNCJPCKAZ","01M7F5607RE7Y5NNRN60FW9NJ3",0,"MIT","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Fbase\u002Ffiles\u002Fforge-gitlab\u002Fskills\u002Fforge-gitlab\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: forge-gitlab\ndescription: \"How each step of the workflow skill is done on GitLab with glab — Issues, merge requests, Closes #n, scoped labels and the one-call status swap GitLab Free needs, the closing-word trap, Draft merge requests, milestones and the board. Activate with the workflow skill whenever it sends you to the forge.\"\n---\n\n# Skill: The workflow on GitLab\n\nThe `workflow` skill says what happens and when; this one says how on GitLab. Its MR is a merge\nrequest here. Use `glab` directly — wf wraps none of it. Where `glab` has a flag for something, use\nit; `glab api` is for the few things it does not cover, named below.\n\n---\n\n## Issues\n\n- **Read one** before touching a file: `glab issue view \u003Cn> --comments`.\n- **Search before creating one:** `glab issue list --search \"\u003Cwords>\"`, and `--all` for closed ones.\n- **Create one** with its labels and milestone from the start:\n  `glab issue create --title \"…\" --description \"…\" --label \"type::feature,area::\u003Carea>,status::todo\" --milestone \"\u003Cname>\"`.\n  A long description goes in a file first: `--description \"$(cat issue.md)\"`.\n- **Comment:** `glab issue note \u003Cn> --message \"…\"`.\n- **Link two Issues:** `--linked-issues \u003Cother>` when creating one; for two that exist,\n  `glab api -X POST \"projects\u002F:id\u002Fissues\u002F\u003Cn>\u002Flinks\" -f target_project_id=\u003Cproject id> -f target_issue_iid=\u003Cother>`.\n  **GitLab Free has no \"blocks\" link**, only \"relates to\", so the order of work is written in each\n  Issue's description, never left to the link.\n\n## Labels: scoped, and not exclusive on Free\n\nEvery label of the workflow skill is a scoped label here: `status::todo`, `status::in progress`,\n`status::in review`, `status::blocked`; `type::feature`, `type::bug`, `type::chore`, `type::docs`,\n`type::decision`; `area::\u003Carea>`.\n\n**On GitLab Free, `::` labels are not mutually exclusive:** GitLab will not remove the old status\nwhen a new one is added. So a status change is **one call** that removes the old label and adds the\nnew one together — never two, which would leave the Issue with both or neither for a moment, and\nwith both for good if the second call fails:\n\n```sh\nglab api -X PUT \"projects\u002F:id\u002Fissues\u002F\u003Cn>\" -f remove_labels=\"status::in progress\" -f add_labels=\"status::in review\"\n```\n\nBefore setting a status, check that the Issue carries exactly one `status::` label\n(`glab issue view \u003Cn>`), and repair it in the same call if a hand edit on the board left two.\n\nThe board has one column per `status::` label. Its columns show open Issues only: a closed Issue\nmoves to \"Closed\" on its own, keeping the status it had.\n\n**A label a CI job reads**, such as `api-passthrough`, which lets the backend's breaking-change job\naccept a break, is a plain one on the merge request: `glab mr update \u003Cn> --label api-passthrough`.\nGitLab reads labels when a pipeline starts, so start a new merge request pipeline after adding\nit: `glab api -X POST \"projects\u002F:id\u002Fmerge_requests\u002F\u003Cn>\u002Fpipelines\"`. Retrying a job, or a branch\npipeline from `glab ci run`, still sees the labels it had.\n\n## Milestones\n\n- **List the open ones** before assigning or creating: `glab api \"projects\u002F:id\u002Fmilestones?state=active\"`.\n- **Create one** only by the workflow skill's rules:\n  `glab api -X POST \"projects\u002F:id\u002Fmilestones\" -f title=\"\u003Cname>\" -f description=\"…\"`.\n- **Assign it:** `glab issue update \u003Cn> --milestone \"\u003Cname>\"`.\n\n## Merge requests\n\n- **Open one as a Draft**, on the developer's go, after the first push:\n  `glab mr create --draft --title \"…\" --description \"…\" --source-branch \u003Cbranch> --target-branch main`.\n  The description carries `Closes #n` from the start: GitLab acts on it at merge, Draft or not.\n- **Take it out of Draft** when the Issue's work is done: `glab mr update \u003Cn> --ready`, together\n  with the status swap above.\n- **Read a review:** `glab mr view \u003Cn> --comments`; the diff with `glab mr diff \u003Cn>`.\n- **Merge** only when asked. Squashed, with the message the workflow skill shapes:\n  `glab mr merge \u003Cn> --squash --squash-message \"$(cat message.md)\"`, where `message.md` holds the\n  whole message, summary line first; without `--squash-message`, GitLab writes its own. Unsquashed,\n  plain `glab mr merge \u003Cn>`. `glab mr merge` sets auto-merge by default, which waits for the\n  pipeline — **but only when a pipeline exists.** With none running (CI minutes used up, say), it\n  merges at once. So check the pipeline first — `glab mr view \u003Cn>` shows it — and say so to the\n  developer when there is none.\n\n## Closing\n\n- `Closes #n` in a merge request description closes the Issue when the merge request merges, as\n  long as the project has auto-close on (*Settings → Repository → Default branch*).\n- **The closing-word trap.** GitLab reads a closing word next to an Issue reference as a command,\n  whatever the words around it: \"does not close #n\" closes #n at merge. A merge request that\n  must not close an Issue writes \"#n stays open until …\", and after the merge checks that the Issue\n  is still open — `glab issue view \u003Cn>` — reopening it with `glab issue reopen \u003Cn>` if GitLab closed\n  it anyway.\n\n## The plan's own merge request\n\nIt carries `Part of #parent` and no closing word next to any Issue number — the parent is closed by\nthe last Issue of the plan, not by the plan.\n","# Skill: The workflow on GitLab\n\nThe `workflow` skill says what happens and when; this one says how on GitLab. Its MR is a merge\nrequest here. Use `glab` directly — wf wraps none of it. Where `glab` has a flag for something, use\nit; `glab api` is for the few things it does not cover, named below.\n\n---\n\n## Issues\n\n- **Read one** before touching a file: `glab issue view \u003Cn> --comments`.\n- **Search before creating one:** `glab issue list --search \"\u003Cwords>\"`, and `--all` for closed ones.\n- **Create one** with its labels and milestone from the start:\n  `glab issue create --title \"…\" --description \"…\" --label \"type::feature,area::\u003Carea>,status::todo\" --milestone \"\u003Cname>\"`.\n  A long description goes in a file first: `--description \"$(cat issue.md)\"`.\n- **Comment:** `glab issue note \u003Cn> --message \"…\"`.\n- **Link two Issues:** `--linked-issues \u003Cother>` when creating one; for two that exist,\n  `glab api -X POST \"projects\u002F:id\u002Fissues\u002F\u003Cn>\u002Flinks\" -f target_project_id=\u003Cproject id> -f target_issue_iid=\u003Cother>`.\n  **GitLab Free has no \"blocks\" link**, only \"relates to\", so the order of work is written in each\n  Issue's description, never left to the link.\n\n## Labels: scoped, and not exclusive on Free\n\nEvery label of the workflow skill is a scoped label here: `status::todo`, `status::in progress`,\n`status::in review`, `status::blocked`; `type::feature`, `type::bug`, `type::chore`, `type::docs`,\n`type::decision`; `area::\u003Carea>`.\n\n**On GitLab Free, `::` labels are not mutually exclusive:** GitLab will not remove the old status\nwhen a new one is added. So a status change is **one call** that removes the old label and adds the\nnew one together — never two, which would leave the Issue with both or neither for a moment, and\nwith both for good if the second call fails:\n\n```sh\nglab api -X PUT \"projects\u002F:id\u002Fissues\u002F\u003Cn>\" -f remove_labels=\"status::in progress\" -f add_labels=\"status::in review\"\n```\n\nBefore setting a status, check that the Issue carries exactly one `status::` label\n(`glab issue view \u003Cn>`), and repair it in the same call if a hand edit on the board left two.\n\nThe board has one column per `status::` label. Its columns show open Issues only: a closed Issue\nmoves to \"Closed\" on its own, keeping the status it had.\n\n**A label a CI job reads**, such as `api-passthrough`, which lets the backend's breaking-change job\naccept a break, is a plain one on the merge request: `glab mr update \u003Cn> --label api-passthrough`.\nGitLab reads labels when a pipeline starts, so start a new merge request pipeline after adding\nit: `glab api -X POST \"projects\u002F:id\u002Fmerge_requests\u002F\u003Cn>\u002Fpipelines\"`. Retrying a job, or a branch\npipeline from `glab ci run`, still sees the labels it had.\n\n## Milestones\n\n- **List the open ones** before assigning or creating: `glab api \"projects\u002F:id\u002Fmilestones?state=active\"`.\n- **Create one** only by the workflow skill's rules:\n  `glab api -X POST \"projects\u002F:id\u002Fmilestones\" -f title=\"\u003Cname>\" -f description=\"…\"`.\n- **Assign it:** `glab issue update \u003Cn> --milestone \"\u003Cname>\"`.\n\n## Merge requests\n\n- **Open one as a Draft**, on the developer's go, after the first push:\n  `glab mr create --draft --title \"…\" --description \"…\" --source-branch \u003Cbranch> --target-branch main`.\n  The description carries `Closes #n` from the start: GitLab acts on it at merge, Draft or not.\n- **Take it out of Draft** when the Issue's work is done: `glab mr update \u003Cn> --ready`, together\n  with the status swap above.\n- **Read a review:** `glab mr view \u003Cn> --comments`; the diff with `glab mr diff \u003Cn>`.\n- **Merge** only when asked. Squashed, with the message the workflow skill shapes:\n  `glab mr merge \u003Cn> --squash --squash-message \"$(cat message.md)\"`, where `message.md` holds the\n  whole message, summary line first; without `--squash-message`, GitLab writes its own. Unsquashed,\n  plain `glab mr merge \u003Cn>`. `glab mr merge` sets auto-merge by default, which waits for the\n  pipeline — **but only when a pipeline exists.** With none running (CI minutes used up, say), it\n  merges at once. So check the pipeline first — `glab mr view \u003Cn>` shows it — and say so to the\n  developer when there is none.\n\n## Closing\n\n- `Closes #n` in a merge request description closes the Issue when the merge request merges, as\n  long as the project has auto-close on (*Settings → Repository → Default branch*).\n- **The closing-word trap.** GitLab reads a closing word next to an Issue reference as a command,\n  whatever the words around it: \"does not close #n\" closes #n at merge. A merge request that\n  must not close an Issue writes \"#n stays open until …\", and after the merge checks that the Issue\n  is still open — `glab issue view \u003Cn>` — reopening it with `glab issue reopen \u003Cn>` if GitLab closed\n  it anyway.\n\n## The plan's own merge request\n\nIt carries `Part of #parent` and no closing word next to any Issue number — the parent is closed by\nthe last Issue of the plan, not by the plan.\n",{"name":5,"description":7},"main","68fb57dd74de5ed76dcfaff357932684f77650e6","internal\u002Fbase\u002Ffiles\u002Fforge-gitlab\u002Fskills\u002Fforge-gitlab","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg","2026-11-13 17:41:05",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add workflowaiorg\u002Fworkflow --skill forge-gitlab",{"tool":35,"command":36},"bunx","bunx skills add workflowaiorg\u002Fworkflow --skill forge-gitlab",{"tool":38,"command":39},"pnpm","pnpm dlx skills add workflowaiorg\u002Fworkflow --skill forge-gitlab","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Fbase\u002Ffiles\u002Fforge-gitlab\u002Fskills\u002Fforge-gitlab\u002FSKILL.md",true,[],[44,51,58,65,72,77],{"skillNo":45,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":48,"categories":49,"keywords":50,"publishedAt":18},"01M7F58YP2QA8F89599TDWEY0Y","notes","Where notes go.","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Frender\u002Ftestdata\u002Fsync\u002Fwant\u002F.opencode\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":18},"01M7F58X62078DBFA7YZH0M9VP","naming","How things are named, including the sample's tables.","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Frender\u002Ftestdata\u002Fsync\u002Fwant\u002F.opencode\u002Fskills\u002Fnaming\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":18},"01M7F58VXX28G09AJCA667GHBS","local","A skill only this project has.","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Frender\u002Ftestdata\u002Fsync\u002Fwant\u002F.opencode\u002Fskills\u002Flocal\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":18},"01M7F58TQ8XVBD6SDV0S4T6E77","hello","Greets sample's developers.","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Frender\u002Ftestdata\u002Fsync\u002Fwant\u002F.opencode\u002Fskills\u002Fhello\u002FSKILL.md",[],[],{"skillNo":73,"name":46,"nameZh":6,"description":47,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7F58R379TW8C6VY572RK11F","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Frender\u002Ftestdata\u002Fsync\u002Fwant\u002F.github\u002Fskills\u002Fnotes\u002FSKILL.md",[],[],{"skillNo":78,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7F58PNRREJ4KPY496M2XHSY","https:\u002F\u002Fgithub.com\u002Fworkflowaiorg\u002Fworkflow\u002Fblob\u002Fmain\u002Finternal\u002Frender\u002Ftestdata\u002Fsync\u002Fwant\u002F.github\u002Fskills\u002Fnaming\u002FSKILL.md",[],[]]