ryanmacleanryanmaclean/skills/gitea-release/SKILL.md

gitea-release

Skill1 starsChanged 50 days agoMITView on GitHub

Create Gitea releases and upload build artifacts via the tea CLI and Gitea API. Use when publishing binaries or packages to a Gitea instance after a version bump.

Reads credentials
Commits and pushes

In this repository113 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ac-ideateSkill
- ac-listSkill
- ac-roadmapSkill
- agentbridge-mcpSkill
- almanacSkill
- almquist-shellSkill
- ansible-fleetSkill
- apfsSkill
- apple-siliconSkill
- arena-actorsSkill
- asustor-nasSkill
- a-teamSkill
- atem-miniSkill
- at-tuiSkill
- autoresearchSkill
- babysitSkill
- bonzibuddySkill
- bop-brainstormSkill
- bop-catalogSkill
- bop-onSkill
- bop-teamSkill
- bop-workflowSkill
- bsd-portabilitySkill
- code-refactoringSkill
- codex-personasSkill
- context-graphSkill
- councilSkill
- datadog-backupSkill
- dd-tagsSkill
- delegateSkill
- deming-pdsaSkill
- deterministic-replaySkill
- dispatch-nuSkill
- durable-commitSkill
- elixir-gastown-opsSkill
- ergo-ircSkill
- esp32-tang-bridgeSkill
- fleet-evalSkill
- fleet-ircSkill
- freebsd-build-vmSkill
- freebsd-piSkill
- freebsdSkill
- ganttSkill
- gastown-opsSkill
- gastown-slingSkill
- gh-authSkill
- gitea-runnerSkill
- henshuSkill
- irclaw-cluster-opsSkill
- irclaw-research-teamSkill
- irc-taskSkill
- jail-factorySkill
- jjSkill
- jobcard-systemSkill
- kubernetesSkill
- leptosSkill
- loreSkill
- lower-bound-reviewSkill
- macvlan-netSkill
- The first 60 shown.

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:
Every tea release create MUST end with a <claims> block:
line 85

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Gitea Release Artifact Upload

As of 2026-04-06. See also tea for repo/issue/PR workflows. See deployment-specific details below for fleet Gitea host coordinates.

Create a release

# via tea CLI
tea release create \
  --repo studio/ii-agent \
  --tag v1.0.0 \
  --title "ii-agent v1.0.0" \
  --note "100 tests, production-ready"

# via raw API (fallback)
tea api -X POST /repos/studio/ii-agent/releases \
  -d '{"tag_name":"v1.0.0","name":"ii-agent v1.0.0","body":"100 tests, production-ready"}'

Upload a single asset

tea release asset create \
  --repo studio/ii-agent \
  --tag v1.0.0 \
  --file ./packages/builds-1.0.0/aarch64-linux-musl/ii-agent

Upload all targets after a build (nushell)

let targets = [
  "aarch64-linux-musl"
  "aarch64-linux-gnu"
  "aarch64-netbsd"
  "x86_64-linux-gnu"
  "aarch64-macos"
]

for t in $targets {
  let src = $"packages/builds-1.0.0/($t)/ii-agent"
  if ($src | path exists) {
    tea release asset create --repo studio/ii-agent --tag v1.0.0 --file $src
  }
}

List releases

tea release list --repo studio/ii-agent

Delete a release (careful)

tea api -X DELETE /repos/studio/ii-agent/releases/<ID>

Common mistakes

Mistake	Fix
Tag doesn't exist yet	Push tag first: `git tag v1.0.0 && git push origin v1.0.0`
Asset name collision	Delete old asset before re-upload or use a suffix
Uploading from Mac to macvlan Gitea	Works from host network; if blocked, hop through the bastion host (see deployment-specific details below)
Embedding token in URL	Use `tea` auth or `~/.netrc` — never in git remotes (see memory)
Over-600MB single asset	Gitea default limit; split or raise `MAX_UPLOAD_SIZE` in Gitea config

tea — full Gitea CLI reference (repos, issues, PRs, code browsing)
ii-agent-ops — upstream build step that produces the artifacts (project-scoped)
macvlan-net — macvlan networking topology (relevant if Gitea runs on a macvlan interface)

Verification contract (REQUIRED for all releases)

Every tea release create MUST end with a <claims> block:

<claims>
- claim: "Release TAG exists on REPO"
  probe: "tea release view --repo studio/REPO --tag TAG"
  expect: "TAG"
- claim: "Asset FILE uploaded"
  probe: "tea release view --repo studio/REPO --tag TAG | grep -c 'FILE'"
  expect: "1"
</claims>

Verdicts via fleet-eval.nu verify. See fleet-eval skill.

Deployment-specific details

This skill is generic Gitea release tooling. Everything above applies to any Gitea instance. Concrete host coordinates live in the deployment's fleet-ops repo.

For the rust-town fleet:

fleet-ops/docs/gitea-ci.md — Gitea instance URLs, runner host table, CI secret conventions, fork-repo locations
Gitea host and bastion hop IPs are in that doc; do not embed them here

Download now (ZIP)

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

What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free