forgejo
Forgejo REST API toolkit — manage issues, pull requests, wikis, and repos on a Forgejo server. Use when the agent needs to file an issue, open / review / merge a PR, read or write a wiki page, or look up repo / branch info. One standalone script per resource type. Reads credentials from environment, `~/.skillhone/settings.json`, or `_data/forgejo_config.txt`.
npx skills add Tencent/SkillHone --skill forgejo --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Forgejo Thin wrapper around the Forgejo REST API. Each resource lives in its own script so the agent can discover and invoke them individually. SkillHone depends on this as a VCS backend skill, but it stays independent so another backend such as GitLab or Gitea can provide the same workflow surface. ## Scripts | Script | Resource | Representative usage | |--------|----------|----------------------| | `scripts/issue.py` | Issues | `python3 scripts/issue.py create --title "Bug"` | | `scripts/pr.py` | Pull requests | `python3 scripts/pr.py merge 1` | | `scripts/wiki.py` | Wiki pages | `python3 scripts/wiki.py get --title "Analysis"` | | `scripts/repo.py` | Repo metadata | `python3 scripts/repo.py branches` | | `scripts/summary.py` | Aggregate dashboard | `python3 scripts/summary.py` | Every script supports `--help`. Run it before guessing flags. ## Configuration Resolved in this order (first match wins): 1. Environment variables: `FORGEJO_URL`, `FORGEJO_TOKEN`, `FORGEJO_OWNER`, `FORGEJO_REPO` 2. `~/.skillhone/settings.json` + `~/.skillhone/identities.conf` 3. `_data/forgejo_config.txt` in the current working directory If nothing is set, the script exits with a clear message naming t
- Scripts
- Configuration
- Usage By Resource
- Issues
- Pull Requests
- Wiki
- Repo Metadata
- Combined Summary
- Invocation From Other Skills
- Gotchas
- Hard Rules
python3 scripts/issue.py list python3 scripts/issue.py view <N> python3 scripts/issue.py create --title "Fix: timeout" --body "## Problem\n..." python3 scripts/issue.py close <N> python3 scripts/issue.py comment <N> --body "Done" python3 scripts/pr.py list python3 scripts/pr.py view <M> python3 scripts/pr.py create --title "Fix timeout" --head fix/timeout --base main --body "Closes #1" python3 scripts/pr.py review <M> --approve python3 scripts/pr.py merge <M> --method merge
What does the forgejo skill do?
Forgejo REST API toolkit — manage issues, pull requests, wikis, and repos on a Forgejo server. Use when the agent needs to file an issue, open / review / merge a PR, read or write a wiki page, or look up repo / branch info. One standalone script per resource type. Reads credentials from environment, `~/.skillhone/settings.json`, or `_data/forgejo_config.txt`.
How do I install it?
Run `npx skills add Tencent/SkillHone --skill forgejo --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Tencent/SkillHone, a repository with 107 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
