createPrReview tool — Well-structured and properly maps the tool parameters to the Forgejo API. The side field handling (BASE vs HEAD) correctly translates to old_position / new_position.
Parameter renaming — Renaming issueNumber/prNumber to issueId/prId across context.ts, forgejo/index.ts, and schemas.ts is a good consistency improvement. The API uses numeric IDs, not GitHub-style issue numbers.
Shared issueStateSchema — Extracting the common state union into a reusable constant avoids duplication between issueSchema and pullRequestSchema.
Tool renaming — Renaming createPullRequest → createPr is consistent with the shorter naming pattern used by other tools (closeIssue, createIssue, etc.).
Prompt update — Correctly updated to reference the new create-pr-review tool name.

🔧 Minor fix applied

I fixed two useImportType lint warnings in src/forgejo/index.ts:

StaticParse → type StaticParse
prReviewEventSchema → type prReviewEventSchema (only used in typeof type context)

📝 Notes

The helper functions (getPrReviews, getPrReview, getPrReviewComments, postPrReviewComment) are unused as you mentioned — they're ready for future use.
The prReviewCommentSchema only has body which is fine for the response parsing.

Overall: LGTM 🚀

Great work on this PR! Here's my review: ## ✅ What looks good 1. **`createPrReview` tool** — Well-structured and properly maps the tool parameters to the Forgejo API. The `side` field handling (BASE vs HEAD) correctly translates to `old_position` / `new_position`. 2. **Parameter renaming** — Renaming `issueNumber`/`prNumber` to `issueId`/`prId` across `context.ts`, `forgejo/index.ts`, and `schemas.ts` is a good consistency improvement. The API uses numeric IDs, not GitHub-style issue numbers. 3. **Shared `issueStateSchema`** — Extracting the common state union into a reusable constant avoids duplication between `issueSchema` and `pullRequestSchema`. 4. **Tool renaming** — Renaming `createPullRequest` → `createPr` is consistent with the shorter naming pattern used by other tools (`closeIssue`, `createIssue`, etc.). 5. **Prompt update** — Correctly updated to reference the new `create-pr-review` tool name. ## 🔧 Minor fix applied I fixed two `useImportType` lint warnings in `src/forgejo/index.ts`: - `StaticParse` → `type StaticParse` - `prReviewEventSchema` → `type prReviewEventSchema` (only used in `typeof` type context) ## 📝 Notes - The helper functions (`getPrReviews`, `getPrReview`, `getPrReviewComments`, `postPrReviewComment`) are unused as you mentioned — they're ready for future use. - The `prReviewCommentSchema` only has `body` which is fine for the response parsing. **Overall: LGTM** 🚀

Ghost added 1 commit

2026-06-27 11:39:12 +00:00

fix(lint): use import type for type-only imports

check-formatter.yaml / Checks with formatters (pull_request) Successful in 7s

Details

check-linter.yaml / Checks with linters (pull_request) Successful in 10s

Details

check-prettier.yaml / Check files formatting (pull_request) Successful in 2s

Details

check-syntax.yaml / Checks with static tools (pull_request) Successful in 16s

Details

check-yamllint.yaml / Lint yaml files (pull_request) Successful in 2s