Files
hermes-agent/skills/software-development/github/references/conventional-commits.md
Teknium c49fa88b80 refactor(skills): shipped-set slim — 15 to optional, github 6-way merge, pdf absorbs OCR, channel-gated teams pipeline (index −26%) (#98539)
* refactor(skills): shipped-set slim — 15 skills to optional, github six-way merge, pdf absorbs OCR+nano-pdf, channel-gated teams pipeline

Maintainer-directed shipped-skills curation (skills index 1,900 -> ~1,400
tok/call on desktop; every session pays the index, so this is a per-call
diet on all installs):

- optional-skills moves (installable via skills hub, history preserved):
  creative comfyui/ascii-art/excalidraw/pretext/sketch/touchdesigner-mcp;
  ALL of mlops (huggingface-hub, llama-cpp, serving-llms-vllm,
  weights-and-biases, evaluating-llms-harness — subcategory structure
  kept); research-paper-writing (55 supporting files, 17.3K-tok load);
  openhue; blogwatcher (first taught the cronjob monitor-field watch
  pattern + web_extract instead of pre-cron manual workflows)
- DELETED session-librarian (Aug-12 'inspired by Perplexity Computer'
  port, never maintainer-intended; session_search covers discovery)
- github: six skills (auth, issues, pr-workflow, issue-to-pr,
  code-review, repo-management) merged into ONE software-development/
  github skill — routing body + complete per-workflow references;
  benbarclay authorship credited; codebase-inspection rides along;
  discipline pins from test_github_issue_to_pr_skill.py preserved
  against the reference body in the new test_github_skill.py
- pdf absorbs ocr-and-documents + nano-pdf as references/ + scripts
  (extract_pymupdf, extract_marker converted to the argparse house
  standard its contract test enforces)
- NEW session_platforms frontmatter gate (metadata.hermes): hides a
  skill from the index on gateway channels it is not for; fail-open on
  unknown platform; teams-meeting-pipeline gated to [teams, cron]
- blocked-page-recovery: research -> new web category; trigger-first
  description ('Use when a fetch fails: 403/429, paywall, WAF, bot
  wall.') so the model actually reaches for it on blocked fetches
- docs regenerated via generate-skill-docs.py (195 pages); related_skills
  swept repo-wide; tests: 1672 passed (2 openclaw failures pre-existing
  on clean main, Windows-local)

* chore: ignore .skills_prompt_snapshot.json (local index cache, accidentally committed)
2026-08-30 04:53:39 -07:00

2.4 KiB

Conventional Commits Quick Reference

Format: type(scope): description

Types

Type When to use Example
feat New feature or capability feat(auth): add OAuth2 login flow
fix Bug fix fix(api): handle null response from /users endpoint
refactor Code restructuring, no behavior change refactor(db): extract query builder into separate module
docs Documentation only docs: update API usage examples in README
test Adding or updating tests test(auth): add integration tests for token refresh
ci CI/CD configuration ci: add Python 3.12 to test matrix
chore Maintenance, dependencies, tooling chore: upgrade pytest to 8.x
perf Performance improvement perf(search): add index on users.email column
style Formatting, whitespace, semicolons style: run black formatter on src/
build Build system or external deps build: switch from setuptools to hatch
revert Reverts a previous commit revert: revert "feat(auth): add OAuth2 login flow"

Scope (optional)

Short identifier for the area of the codebase: auth, api, db, ui, cli, etc.

Breaking Changes

Add ! after type or BREAKING CHANGE: in footer:

feat(api)!: change authentication to use bearer tokens

BREAKING CHANGE: API endpoints now require Bearer token instead of API key header.
Migration guide: https://docs.example.com/migrate-auth

Multi-line Body

Wrap at 72 characters. Use bullet points for multiple changes:

feat(auth): add JWT-based user authentication

- Add login/register endpoints with input validation
- Add User model with argon2 password hashing
- Add auth middleware for protected routes
- Add token refresh endpoint with rotation

Closes #42

Linking Issues

In the commit body or footer:

Closes #42          ← closes the issue when merged
Fixes #42           ← same effect
Refs #42            ← references without closing
Co-authored-by: Name <email>

Quick Decision Guide

  • Added something new? → feat
  • Something was broken and you fixed it? → fix
  • Changed how code is organized but not what it does? → refactor
  • Only touched tests? → test
  • Only touched docs? → docs
  • Updated CI/CD pipelines? → ci
  • Updated dependencies or tooling? → chore
  • Made something faster? → perf