From caf14785a7aa8e82737e885c3d002a766f987cb0 Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Sun, 5 Jul 2026 11:25:59 -0700 Subject: [PATCH] refactor(skills): make PR creation forge-agnostic in finishing-a-development-branch Naming gh and glab implicitly blessed two forges; Gitea, Forgejo, Bitbucket and others are equally valid. Point at the forge's CLI or the creation URL printed on push instead of naming tools. --- skills/finishing-a-development-branch/SKILL.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/skills/finishing-a-development-branch/SKILL.md b/skills/finishing-a-development-branch/SKILL.md index 368829fd..e25420bc 100644 --- a/skills/finishing-a-development-branch/SKILL.md +++ b/skills/finishing-a-development-branch/SKILL.md @@ -129,10 +129,10 @@ git branch -d git push -u origin ``` -Then create the pull/merge request against with the host's -tooling (`gh pr create`, `glab mr create`, or the URL git prints on push), -following the repo's PR template and conventions if present, and report -the URL to your human partner. +Then create the pull/merge request against with the forge's +tooling — its CLI if one is available, or the creation URL most forges +print when you push — following the repo's PR template and conventions if +present, and report the URL to your human partner. **Do NOT clean up worktree** — user needs it alive to iterate on PR feedback.