issue-49: prefer forgejo extension tools over fj CLI #50

Owner

Updates the skills in this repo to prefer the forgejo pi extension tools over the fj CLI for Forgejo operations. The extension calls the Forgejo REST API directly with structured arguments — no shell interpolation — so content with $, backticks, quotes, emoji, or newlines is never mangled (the fj escaping bug is fixed by construction). fj remains documented as the fallback for anything the extension doesn't cover (repo create/clone, releases, tags, wiki).

What & why: the issue → branch → commit/push → PR → merge workflow skills (commit-docs, commit-changes, furnish-repo, init-project) used fj for every Forgejo remote operation. They now use forgejo_issue_create, forgejo_pr_create, forgejo_pr_merge, forgejo_list_labels, forgejo_label_create, and forgejo_detect (auth check), with fj kept only in explicit fallback blocks.

Per-file breakdown:

Modified:

  • skills/commit-docs/SKILL.md — dispatch table + issue/PR/merge steps prefer the extension; forgejo_detect auth check; references updated
  • skills/commit-changes/SKILL.md — same treatment as commit-docs, plus issue-closed verification via forgejo_issue_view/forgejo_issue_close
  • skills/furnish-repo/SKILL.md — label audit/creation (forgejo_list_labels/forgejo_label_create), issue, PR, merge → extension; quick-reference updated
  • skills/init-project/SKILL.md — labels, setup issue, PR creation → extension; fj retained (with notes) for repo create/clone, which the extension doesn't cover
  • skills/tdd-implementation/SKILL.md — PR tooling detection → extension preferred, fj fallback
  • skills/create-issues/SKILL.md — fixed stale "extension lacks milestone/label tools" dependency section (they now exist); fj whoamiforgejo_detect
  • skills/forgejo-cli/SKILL.md — added "prefer the forgejo pi extension" callout; remains the fj fallback reference

Closes #49

Updates the skills in this repo to prefer the `forgejo` pi extension tools over the `fj` CLI for Forgejo operations. The extension calls the Forgejo REST API directly with structured arguments — no shell interpolation — so content with `$`, backticks, quotes, emoji, or newlines is never mangled (the `fj` escaping bug is fixed by construction). `fj` remains documented as the fallback for anything the extension doesn't cover (repo create/clone, releases, tags, wiki). **What & why:** the issue → branch → commit/push → PR → merge workflow skills (commit-docs, commit-changes, furnish-repo, init-project) used `fj` for every Forgejo remote operation. They now use `forgejo_issue_create`, `forgejo_pr_create`, `forgejo_pr_merge`, `forgejo_list_labels`, `forgejo_label_create`, and `forgejo_detect` (auth check), with `fj` kept only in explicit fallback blocks. **Per-file breakdown:** Modified: - `skills/commit-docs/SKILL.md` — dispatch table + issue/PR/merge steps prefer the extension; `forgejo_detect` auth check; references updated - `skills/commit-changes/SKILL.md` — same treatment as commit-docs, plus issue-closed verification via `forgejo_issue_view`/`forgejo_issue_close` - `skills/furnish-repo/SKILL.md` — label audit/creation (`forgejo_list_labels`/`forgejo_label_create`), issue, PR, merge → extension; quick-reference updated - `skills/init-project/SKILL.md` — labels, setup issue, PR creation → extension; `fj` retained (with notes) for repo create/clone, which the extension doesn't cover - `skills/tdd-implementation/SKILL.md` — PR tooling detection → extension preferred, `fj` fallback - `skills/create-issues/SKILL.md` — fixed stale "extension lacks milestone/label tools" dependency section (they now exist); `fj whoami` → `forgejo_detect` - `skills/forgejo-cli/SKILL.md` — added "prefer the forgejo pi extension" callout; remains the `fj` fallback reference Closes #49
david merged commit 1c016169e3 into main 2026-08-18 22:24:35 +00:00
david deleted branch documentation/issue-49/commit-working-tree-changes-prefer-forgejo-extension-tools-over-fj-cli 2026-08-18 22:24:36 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
david/pi-extensions-and-skills!50
No description provided.