gitea: v1.1.0 — add versioning policy, bump version in commit messages

This commit is contained in:
Hermes Agent
2026-07-04 13:38:05 -05:00
parent 046de9e502
commit 133d3d8b07

View File

@@ -1,7 +1,7 @@
--- ---
name: gitea name: gitea
description: "Push Hermes skill updates to the local Gitea instance at 10.0.0.61:3000. Clone, copy, commit, push workflow." description: "Push Hermes skill updates to the local Gitea instance at 10.0.0.61:3000. Clone, copy, commit, push workflow."
version: 1.0.0 version: 1.1.0
author: Hermes Agent author: Hermes Agent
license: MIT license: MIT
platforms: [linux] platforms: [linux]
@@ -26,6 +26,17 @@ Push skill updates to the local Gitea instance at `http://10.0.0.61:3000`.
| Local clone | `/tmp/hermes-skills` | | Local clone | `/tmp/hermes-skills` |
| Skill source | `~/.hermes/profiles/general/skills/` | | Skill source | `~/.hermes/profiles/general/skills/` |
## Versioning
Every skill in the repo MUST have a `version:` field in its YAML frontmatter.
Before pushing, always check and bump the version:
| Change type | Bump | Example |
|---|---|---|
| Fixes, clarifications, pitfall additions | patch | 1.0.0 → 1.0.1 |
| New features, new sections, new references | minor | 1.0.0 → 1.1.0 |
| Rewrites, major restructuring | major | 1.0.0 → 2.0.0 |
## Workflow ## Workflow
### Push Updated Skills ### Push Updated Skills
@@ -38,12 +49,18 @@ cd /tmp && git clone http://10.0.0.61:3000/SpeedyFoxAi/hermes-skills.git
# 2. Copy updated skill files from the active profile # 2. Copy updated skill files from the active profile
cp ~/.hermes/profiles/general/skills/<category>/<skill-name>/SKILL.md /tmp/hermes-skills/<skill-name>/SKILL.md cp ~/.hermes/profiles/general/skills/<category>/<skill-name>/SKILL.md /tmp/hermes-skills/<skill-name>/SKILL.md
# 3. Commit # 3. Bump the version in the copied SKILL.md frontmatter
# Edit /tmp/hermes-skills/<skill-name>/SKILL.md and increment version:
# - patch: fixes, clarifications, pitfall additions
# - minor: new features, new sections, new references
# - major: rewrites, major restructuring
# 4. Commit with version in message
cd /tmp/hermes-skills cd /tmp/hermes-skills
git add <skill-name>/SKILL.md git add <skill-name>/SKILL.md
git commit -m "<message>" git commit -m "<skill-name>: v<new-version> — <brief description>"
# 4. Push with token # 5. Push with token
git remote set-url origin http://2c6cacb89b8124a98a52206fdbee51cefcd46844@10.0.0.61:3000/SpeedyFoxAi/hermes-skills.git git remote set-url origin http://2c6cacb89b8124a98a52206fdbee51cefcd46844@10.0.0.61:3000/SpeedyFoxAi/hermes-skills.git
git push origin main git push origin main
``` ```
@@ -54,8 +71,12 @@ git push origin main
cd /tmp/hermes-skills cd /tmp/hermes-skills
mkdir <skill-name> mkdir <skill-name>
cp ~/.hermes/profiles/general/skills/<category>/<skill-name>/SKILL.md <skill-name>/SKILL.md cp ~/.hermes/profiles/general/skills/<category>/<skill-name>/SKILL.md <skill-name>/SKILL.md
# Verify the SKILL.md has a version: field in its frontmatter.
# New skills should start at 1.0.0.
git add <skill-name>/ git add <skill-name>/
git commit -m "Add <skill-name> skill" git commit -m "Add <skill-name> v1.0.0"
git push origin main git push origin main
``` ```