Use CLI tools

ReadyPlayerNaN commented

2026-03-19 11:07:38 +00:00

Owner

The loop should instruct that before using the remote APIs directly, it should use the local CLI tools, like gh (github cli), glab (gitlab cli), fj (forgejo cli).

ReadyPlayerNaN commented

2026-03-19 11:18:07 +00:00

Author

Owner

I've picked up this issue and I'm reviewing it now.

ReadyPlayerNaN commented

2026-03-19 11:18:36 +00:00

Author

Owner

Triage Assessment

What's clear: The document should establish that CLI tools (gh, glab, fj) are the preferred way to interact with the platform, with raw API calls as a fallback only when the CLI doesn't support an operation.

Scope: Update the Working Context section to establish this preference hierarchy.

No clarifying questions — the intent is clear. Proceeding to planning.

## Triage Assessment **What's clear:** The document should establish that CLI tools (`gh`, `glab`, `fj`) are the preferred way to interact with the platform, with raw API calls as a fallback only when the CLI doesn't support an operation. **Scope:** Update the Working Context section to establish this preference hierarchy. **No clarifying questions** — the intent is clear. Proceeding to planning.

ReadyPlayerNaN added the

planning

label

2026-03-19 11:18:45 +00:00

ReadyPlayerNaN commented

2026-03-19 11:19:05 +00:00

Author

Owner

Plan

Goal: Establish CLI tools as the preferred interface for platform operations, with raw API calls as a fallback.

Approach: Update the Working Context section in merge-request-flow.md to define a clear preference hierarchy: CLI first, API second.

Tasks:

Update the platform detection section to reframe CLI tools as the primary interface rather than just one option. After the platform list, add a paragraph stating: "Prefer CLI tools for all operations they support (creating issues, merge requests, comments, reviews, etc.). Use the platform's REST API directly only for operations the CLI does not support (e.g., adding labels, checking reactions, verifying permissions)."
Add fj to the Forgejo/Gitea bullet — currently it says "Use the Forgejo/Gitea API or a compatible CLI". Change to: "Use fj or tea CLI. Terminology: 'merge requests'." to be consistent with the GitHub/GitLab bullets that name specific tools.

Risks:

Naming specific CLI tools (fj, tea) may be too prescriptive if the user has a different tool. Mitigate by saying "or a compatible CLI" as a fallback.

Test strategy:

Verify the updated section clearly establishes CLI > API preference.
Verify consistency across all three platform bullets.

## Plan **Goal:** Establish CLI tools as the preferred interface for platform operations, with raw API calls as a fallback. **Approach:** Update the Working Context section in `merge-request-flow.md` to define a clear preference hierarchy: CLI first, API second. **Tasks:** 1. **Update the platform detection section** to reframe CLI tools as the primary interface rather than just one option. After the platform list, add a paragraph stating: "Prefer CLI tools for all operations they support (creating issues, merge requests, comments, reviews, etc.). Use the platform's REST API directly only for operations the CLI does not support (e.g., adding labels, checking reactions, verifying permissions)." 2. **Add `fj` to the Forgejo/Gitea bullet** — currently it says "Use the Forgejo/Gitea API or a compatible CLI". Change to: "Use `fj` or `tea` CLI. Terminology: 'merge requests'." to be consistent with the GitHub/GitLab bullets that name specific tools. **Risks:** - Naming specific CLI tools (`fj`, `tea`) may be too prescriptive if the user has a different tool. Mitigate by saying "or a compatible CLI" as a fallback. **Test strategy:** - Verify the updated section clearly establishes CLI > API preference. - Verify consistency across all three platform bullets.

👍 1

ReadyPlayerNaN added

implementing

and removed

planning

labels

2026-03-19 11:19:16 +00:00

ReadyPlayerNaN referenced this issue from a commit

2026-03-19 11:20:17 +00:00

docs: prefer CLI tools over raw API calls

ReadyPlayerNaN referenced this issue from a pull request that will close it,

2026-03-19 11:20:25 +00:00