gitea-repo-management
Skill1 starsChanged 3 months agoMITView on GitHub
Clone/create/fork repos; manage remotes, releases.
- Reads credentials
- Sends data out
- Commits and pushes
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apple-notesSkill
- apple-remindersSkill
- findmySkill
- imessageSkill
- alice-agentSkill
- claude-codeSkill
- codexSkill
- opencodeSkill
- computer-useSkill
- architecture-diagramSkill
- ascii-artSkill
- ascii-videoSkill
- baoyu-infographicSkill
- claude-designSkill
- comfyuiSkill
- design-mdSkill
- excalidrawSkill
- humanizerSkill
- manim-videoSkill
- p5jsSkill
- popular-web-designsSkill
- pretextSkill
- sketchSkill
- songwriting-and-ai-musicSkill
- touchdesigner-mcpSkill
- jupyter-live-kernelSkill
- dogfoodSkill
- himalayaSkill
- codebase-inspectionSkill
- gitea-authSkill
- gitea-code-reviewSkill
- gitea-issuesSkill
- gitea-pr-workflowSkill
- codebase-inspectionSkill
- github-authSkill
- github-code-reviewSkill
- github-issuesSkill
- github-pr-workflowSkill
- github-repo-managementSkill
- codebase-inspectionSkill
- gitlab-authSkill
- gitlab-code-reviewSkill
- gitlab-issuesSkill
- gitlab-mr-workflowSkill
- gitlab-repo-managementSkill
- gif-searchSkill
- heartmulaSkill
- songseeSkill
- youtube-contentSkill
- huggingface-hubSkill
- obsidianSkill
- airtableSkill
- google-workspaceSkill
- mapsSkill
- nano-pdfSkill
- notionSkill
- ocr-and-documentsSkill
- petdexSkill
- powerpointSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 16
Create, clone, fork, configure, and manage GitHub repositories.
- Distinctive: line 46
If you're inside a repo already:
≈ “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
Gitea Repository Management
Create, clone, fork, configure, and manage GitHub repositories. Each section shows tea first, then the git + curl fallback.
Prerequisites
- Authenticated with Gitea (see
gitea-authskill)
Setup
if command -v tea &>/dev/null && tea logins list &>/dev/null; then
AUTH="tea"
else
AUTH="git"
if [ -z "$GITEA_TOKEN" ]; then
if _alice_env="${ALICE_HOME:-$HOME/.alice}/.env"; [ -f "$_alice_env" ] && grep -q "^GITEA_TOKEN=" "$_alice_env"; then
GITEA_TOKEN=$(grep "^GITEA_TOKEN=" "$_alice_env" | head -1 | cut -d= -f2 | tr -d '\n\r')
elif grep -q "github.com" ~/.git-credentials 2>/dev/null; then
GITEA_TOKEN=$(grep "github.com" ~/.git-credentials 2>/dev/null | head -1 | sed 's|https://[^:]*:\([^@]*\)@.*|\1|')
fi
fi
fi
# Get your GitHub username (needed for several operations)
if [ "$AUTH" = "tea" ]; then
TEA_USER=$(tea api user --jq '.login')
else
TEA_USER=$(curl -s -H "Authorization: token $GITEA_TOKEN" https://\${GITEA_HOST:-gitea.com}/api/v1/user | python3 -c "import sys,json; print(json.load(sys.stdin)['login'])")
fiIf you're inside a repo already:
REMOTE_URL=$(git remote get-url origin)
OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's|.*${GITEA_HOST:-gitea\.com}[:/]||; s|\.git$||')
OWNER=$(echo "$OWNER_REPO" | cut -d/ -f1)
REPO=$(echo "$OWNER_REPO" | cut -d/ -f2)1. Cloning Repositories
Cloning is pure git — works identically either way:
# Clone via HTTPS (works with credential helper or token-embedded URL)
git clone https://\${GITEA_HOST:-gitea.com}/owner/repo-name.git
# Clone into a specific directory
git clone https://\${GITEA_HOST:-gitea.com}/owner/repo-name.git ./my-local-dir
# Shallow clone (faster for large repos)
git clone --depth 1 https://\${GITEA_HOST:-gitea.com}/owner/repo-name.git
# Clone a specific branch
git clone --branch develop https://\${GITEA_HOST:-gitea.com}/owner/repo-name.git
# Clone via SSH (if SSH is configured)
git clone git@github.com:owner/repo-name.gitWith tea (shorthand):
tea repo clone owner/repo-name
tea repo clone owner/repo-name -- --depth 12. Creating Repositories
With tea:
# Create a public repo and clone it
tea repos create my-new-project --public --clone
# Private, with description and license
tea repos create my-new-project --private --description "A useful tool" --license MIT --clone
# Under an organization
tea repos create my-org/my-new-project --public --clone
# From existing local directory
cd /path/to/existing/project
tea repos create my-project --source . --public --pushWith git + curl:
# Create the remote repo via API
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/user/repos \
-d '{
"name": "my-new-project",
"description": "A useful tool",
"private": false,
"auto_init": true,
"license_template": "mit"
}'
# Clone it
git clone https://\${GITEA_HOST:-gitea.com}/$TEA_USER/my-new-project.git
cd my-new-project
# -- OR -- push an existing local directory to the new repo
cd /path/to/existing/project
git init
git add .
git commit -m "Initial commit"
git remote add origin https://\${GITEA_HOST:-gitea.com}/$TEA_USER/my-new-project.git
git push -u origin mainTo create under an organization:
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/orgs/my-org/repos \
-d '{"name": "my-new-project", "private": false}'From a Template
With tea:
tea repos create my-new-app --template owner/template-repo --public --cloneWith curl:
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/owner/template-repo/generate \
-d '{"owner": "'"$TEA_USER"'", "name": "my-new-app", "private": false}'3. Forking Repositories
With tea:
tea repo fork owner/repo-name --cloneWith git + curl:
# Create the fork via API
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/owner/repo-name/forks
# Wait a moment for GitHub to create it, then clone
sleep 3
git clone https://\${GITEA_HOST:-gitea.com}/$TEA_USER/repo-name.git
cd repo-name
# Add the original repo as "upstream" remote
git remote add upstream https://\${GITEA_HOST:-gitea.com}/owner/repo-name.gitKeeping a Fork in Sync
# Pure git — works everywhere
git fetch upstream
git checkout main
git merge upstream/main
git push origin mainWith tea (shortcut):
tea repo sync $TEA_USER/repo-name4. Repository Information
With tea:
tea repo view owner/repo-name
tea repos list --limit 20
tea repos search "machine learning" --language python --sort starsWith curl:
# View repo details
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO \
| python3 -c "
import sys, json
r = json.load(sys.stdin)
print(f\"Name: {r['full_name']}\")
print(f\"Description: {r['description']}\")
print(f\"Stars: {r['stargazers_count']} Forks: {r['forks_count']}\")
print(f\"Default branch: {r['default_branch']}\")
print(f\"Language: {r['language']}\")"
# List your repos
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
"https://\${GITEA_HOST:-gitea.com}/api/v1/user/repos?per_page=20&sort=updated" \
| python3 -c "
import sys, json
for r in json.load(sys.stdin):
vis = 'private' if r['private'] else 'public'
print(f\" {r['full_name']:40} {vis:8} {r.get('language', ''):10} ★{r['stargazers_count']}\")"
# Search repos
curl -s \
"https://\${GITEA_HOST:-gitea.com}/api/v1/search/repositories?q=machine+learning+language:python&sort=stars&per_page=10" \
| python3 -c "
import sys, json
for r in json.load(sys.stdin)['items']:
print(f\" {r['full_name']:40} ★{r['stargazers_count']:6} {r['description'][:60] if r['description'] else ''}\")"5. Repository Settings
With tea:
tea repo edit --description "Updated description" --visibility public
tea repo edit --enable-wiki=false --enable-issues=true
tea repo edit --default-branch main
tea repo edit --add-topic "machine-learning,python"
tea repo edit --enable-auto-mergeWith curl:
curl -s -X PATCH \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO \
-d '{
"description": "Updated description",
"has_wiki": false,
"has_issues": true,
"allow_auto_merge": true
}'
# Update topics
curl -s -X PUT \
-H "Authorization: token $GITEA_TOKEN" \
-H "Accept: application/vnd.github.mercy-preview+json" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/topics \
-d '{"names": ["machine-learning", "python", "automation"]}'6. Branch Protection
# View current protection
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/branches/main/protection
# Set up branch protection
curl -s -X PUT \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/branches/main/protection \
-d '{
"required_status_checks": {
"strict": true,
"contexts": ["ci/test", "ci/lint"]
},
"enforce_admins": false,
"required_pull_request_reviews": {
"required_approving_review_count": 1
},
"restrictions": null
}'7. Secrets Management (GitHub Actions)
With tea:
tea secret set API_KEY --body "your-secret-value"
tea secret set SSH_KEY < ~/.ssh/id_rsa
tea secret list
tea secret delete API_KEYWith curl:
Secrets require encryption with the repo's public key — more involved via API:
# Get the repo's public key for encrypting secrets
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/secrets/public-key
# Encrypt and set (requires Python with PyNaCl)
python3 -c "
from base64 import b64encode
from nacl import encoding, public
import json, sys
# Get the public key
key_id = '<key_id_from_above>'
public_key = '<base64_key_from_above>'
# Encrypt
sealed = public.SealedBox(
public.PublicKey(public_key.encode('utf-8'), encoding.Base64Encoder)
).encrypt('your-secret-value'.encode('utf-8'))
print(json.dumps({
'encrypted_value': b64encode(sealed).decode('utf-8'),
'key_id': key_id
}))"
# Then PUT the encrypted secret
curl -s -X PUT \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/secrets/API_KEY \
-d '<output from python script above>'
# List secrets (names only, values hidden)
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/secrets \
| python3 -c "
import sys, json
for s in json.load(sys.stdin)['secrets']:
print(f\" {s['name']:30} updated: {s['updated_at']}\")"Note: For secrets, tea secret set is dramatically simpler. If setting secrets is needed and tea isn't available, recommend installing it for just that operation.
8. Releases
With tea:
tea release create v1.0.0 --title "v1.0.0" --generate-notes
tea release create v2.0.0-rc1 --draft --prerelease --generate-notes
tea release create v1.0.0 ./dist/binary --title "v1.0.0" --notes "Release notes"
tea release list
tea release download v1.0.0 --dir ./downloadsWith curl:
# Create a release
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/releases \
-d '{
"tag_name": "v1.0.0",
"name": "v1.0.0",
"body": "## Changelog\n- Feature A\n- Bug fix B",
"draft": false,
"prerelease": false,
"generate_release_notes": true
}'
# List releases
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/releases \
| python3 -c "
import sys, json
for r in json.load(sys.stdin):
tag = r.get('tag_name', 'no tag')
print(f\" {tag:15} {r['name']:30} {'draft' if r['draft'] else 'published'}\")"
# Upload a release asset (binary file)
RELEASE_ID=<id_from_create_response>
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
-H "Content-Type: application/octet-stream" \
"https://uploads.github.com/repos/$OWNER/$REPO/releases/$RELEASE_ID/assets?name=binary-amd64" \
--data-binary @./dist/binary-amd649. GitHub Actions Workflows
With tea:
tea workflow list
tea ci list --limit 10
tea ci view <RUN_ID>
tea ci view <RUN_ID> --log-failed
tea run rerun <RUN_ID>
tea run rerun <RUN_ID> --failed
tea workflow run ci.yml --ref main
tea workflow run deploy.yml -f environment=stagingWith curl:
# List workflows
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/workflows \
| python3 -c "
import sys, json
for w in json.load(sys.stdin)['workflows']:
print(f\" {w['id']:10} {w['name']:30} {w['state']}\")"
# List recent runs
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
"https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/runs?per_page=10" \
| python3 -c "
import sys, json
for r in json.load(sys.stdin)['workflow_runs']:
print(f\" Run {r['id']} {r['name']:30} {r['conclusion'] or r['status']}\")"
# Download failed run logs
RUN_ID=<run_id>
curl -s -L \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/runs/$RUN_ID/logs \
-o /tmp/ci-logs.zip
cd /tmp && unzip -o ci-logs.zip -d ci-logs
# Re-run a failed workflow
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/runs/$RUN_ID/rerun
# Re-run only failed jobs
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/runs/$RUN_ID/rerun-failed-jobs
# Trigger a workflow manually (workflow_dispatch)
WORKFLOW_ID=<workflow_id_or_filename>
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/repos/$OWNER/$REPO/actions/workflows/$WORKFLOW_ID/dispatches \
-d '{"ref": "main", "inputs": {"environment": "staging"}}'10. Gists
With tea:
tea gist create script.py --public --desc "Useful script"
tea gist listWith curl:
# Create a gist
curl -s -X POST \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/gists \
-d '{
"description": "Useful script",
"public": true,
"files": {
"script.py": {"content": "print(\"hello\")"}
}
}'
# List your gists
curl -s \
-H "Authorization: token $GITEA_TOKEN" \
https://\${GITEA_HOST:-gitea.com}/api/v1/gists \
| python3 -c "
import sys, json
for g in json.load(sys.stdin):
files = ', '.join(g['files'].keys())
print(f\" {g['id']} {g['description'] or '(no desc)':40} {files}\")"Quick Reference Table
| Action | tea | git + curl |
| Clone | tea repo clone o/r | git clone https://\${GITEA_HOST:-gitea.com}/o/r.git |
| Create repo | tea repos create name --public | curl POST /user/repos |
| Fork | tea repo fork o/r --clone | curl POST /repos/o/r/forks + git clone |
| Repo info | tea repo view o/r | curl GET /repos/o/r |
| Edit settings | tea repo edit --... | curl PATCH /repos/o/r |
| Create release | tea release create v1.0 | curl POST /repos/o/r/releases |
| List workflows | tea workflow list | curl GET /repos/o/r/actions/workflows |
| Rerun CI | tea run rerun ID | curl POST /repos/o/r/actions/runs/ID/rerun |
| Set secret | tea secret set KEY | curl PUT /repos/o/r/actions/secrets/KEY (+ encryption) |
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.

