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

@@ -129,10 +129,10 @@ git branch -d <feature-branch>
 git push -u origin <feature-branch>
 ```
 
-Then create the pull/merge request against <base-branch> 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 <base-branch> 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.