Files

Defame1297 f21a1427f5 fix(gitea): correct issue auto-close gotcha, drop unused tool

The gotcha claimed Gitea never auto-closes issues on merge. Confirmed
empirically (issue #63 / PR #64) that a regular merge preserving an
original commit's closing keyword does auto-close — only squash merges
(this skill's default) are unreliable. Also drops search_issues from
allowed-tools since no dispatch route calls it.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-05 09:34:47 +00:00

references

chore: move gitea to bin

2026-06-26 20:04:38 +00:00

README.md

chore: move gitea to bin

2026-06-26 20:04:38 +00:00

SKILL.md

fix(gitea): correct issue auto-close gotcha, drop unused tool

2026-07-05 09:34:47 +00:00

README.md

gitea

Dispatch skill for managing a Gitea repo — issues, PRs, milestones, labels, and branches — from within Claude Code.

Files

File	Purpose
`SKILL.md`	Skill definition — dispatch table, gotchas, execution steps
`references/token-access.md`	Token scope inventory — what works vs. what needs additional scopes

Usage

/gitea                          # status: open issues + open PRs
/gitea issue                    # create issue from conversation context
/gitea issue <N>                # get issue details
/gitea issue close <N>          # close issue
/gitea issue comment <N>        # add comment from conversation context
/gitea label <N> Kind/Bug       # apply labels by name (resolves IDs automatically)
/gitea milestone                # list milestones
/gitea milestone create <title> # create milestone
/gitea pr                       # create PR from current branch → main
/gitea pr <N>                   # get PR status and diff summary
/gitea pr merge <N>             # squash-merge PR, delete branch
/gitea branch                   # list branches
/gitea branch create <name>     # create branch from current branch

Requirements

Gitea MCP server configured in ~/.claude.json with write:issue and write:repository token scopes
git remote origin pointing to the Gitea instance (used to derive owner/repo at runtime)

Scope (v1)

In scope: issues, milestones, labels, PRs, branches, status. Out of scope: releases, CI/Actions, wiki, file operations, notifications, packages, time tracking.