forgejo-issue
Skill1 starsChanged 54 days agoMITView on GitHub
Create, view, edit, comment, assign, close, search issues on a Forgejo repo via fj.
In this repository28 other files it gives its agents.
- journal-coachSkill
- github-templatesSkill
- node-ciSkill
- renovateSkill
- create-readmeSkill
- markdown-styleSkill
- mermaid-syntaxSkill
- obsidian-vaultSkill
- ste100Skill
- forge-detectSkill
- forgejo-prSkill
- web-frontendSkill
- docker-pythonSkill
- pyproject-tomlSkill
- python-ciSkill
- python-cliSkill
- python-devcontainerSkill
- python-projectSkill
- architecture-briefSkill
- design-advisorSkill
- saas-anti-pattern-reviewSkill
- saas-transition-chain-reviewSkill
- saas-transition-reviewSkill
- saas-transition-strategySkill
- security-reviewerSkill
- technical-debt-reviewSkill
- commit-messageSkill
- discord-sendSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Use --no-template if blank issues are allowed.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Setup
fj auth list must show an authenticated session.
Pass --repo owner/repo or -R/--remote origin to target a repo.
Create
fj issue templates --repo owner/repoFill body from template sections in /tmp/issue-body.md, then:
fj issue create --repo owner/repo --template <key> --title "<title>" --body-file /tmp/issue-body.mdUse --no-template if blank issues are allowed.
View
fj issue view <ID>
fj issue view <ID> body
fj issue view <ID> comments
fj issue view <ID> comment <N>Edit
fj issue edit <ID> title "<title>"
fj issue edit <ID> body --body-file <file>
fj issue edit <ID> labels --add <label> --rm <label>
fj issue edit <ID> comment <N> --body-file <file>Comment
fj issue comment <ID> "<text>"
fj issue comment <ID> --body-file <file>Assign
fj issue assign <ID> <user> [user...]
fj issue unassign <ID> <user> [user...]Close
fj issue close <ID>
fj issue close -w "reason" <ID>Search
fj issue search [query] [--labels <l>] [--creator <u>] [--assignee <u>] [--state open|closed|all]Browse
fj issue browse <ID>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

