create `/fix` skill to fix `/code-review` comments #82

New issue

Open

opened 2026-03-06 09:16:16 +00:00 by choucavalier · 4 comments

choucavalier commented

2026-03-06 09:16:16 +00:00

(Migrated from codeberg.org)

once https://codeberg.org/forgejo/forgejo/pulls/11529 is merged, we'll be able to resolve / unresolve comments within that skill

goern commented

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

(Migrated from codeberg.org)

@choucavalier sorry for the discussion on PR 11529 ... forgejo community is not very ai-friendly...

choucavalier commented

2026-03-20 07:36:49 +00:00

(Migrated from codeberg.org)

@goern yes i did not expect that but i think i understand their view. i think we can close this because they closed my PR

harrysummer commented

2026-04-22 17:38:22 +00:00

(Migrated from codeberg.org)

I was trying to develop PR review and fix agents and I encounter this limitation.

If I understand correctly, the Forgejo AI Agreement mentioned in forgejo/forgejo#11529 only applies to the pull requests made to Forgejo code. So we still have a chance here to draft changes to Forgejo without using AI tools?

I was trying to develop PR review and fix agents and I encounter this limitation. If I understand correctly, the Forgejo [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md) mentioned in [forgejo/forgejo#11529](https://codeberg.org/forgejo/forgejo/pulls/11529) only applies to the pull requests made to Forgejo code. So we still have a chance here to draft changes to Forgejo without using AI tools?

goern commented

2026-04-24 14:25:28 +00:00

(Migrated from codeberg.org)

@harrysummer — thanks for flagging this! 👋

That matches my reading of the AI Agreement: it governs contributions to Forgejo itself, so a human-authored PR adding the resolve/unresolve review comment endpoints should still be fair game. PR #11529 was closed, so anyone picking this up would need to start fresh.

If you (or anyone else watching) wants to drive a hand-written upstream implementation, I'm happy to coordinate here and wire the /fix skill up as soon as the endpoints land. Until then this stays Status/Blocked.

Cheers!

@harrysummer — thanks for flagging this! 👋 That matches my reading of the [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md): it governs contributions **to Forgejo itself**, so a human-authored PR adding the resolve/unresolve review comment endpoints should still be fair game. [PR #11529](https://codeberg.org/forgejo/forgejo/pulls/11529) was closed, so anyone picking this up would need to start fresh. If you (or anyone else watching) wants to drive a hand-written upstream implementation, I'm happy to coordinate here and wire the `/fix` skill up as soon as the endpoints land. Until then this stays `Status/Blocked`. Cheers!

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

agentic-forges/forgejo-mcp#82

No description provided.

Rows
Columns

create /fix skill to fix /code-review comments #82

create `/fix` skill to fix `/code-review` comments #82