Borrowing it
Nothing to install: this file belongs to Vasallo94/obsidian-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vasallo94/obsidian-mcp-server/main/.agents/skills/git-workflow/SKILL.mdgit clone --depth 1 https://github.com/Vasallo94/obsidian-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/git-workflow)<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/git-workflow"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/git-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vasallo94/obsidian-mcp-server/git-workflow"><img src="https://agentmods.dev/badge/skills/vasallo94/obsidian-mcp-server/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00804 |
| Opus 5.5 | $0.00013 | $0.00322 |
| Sonnet 5.5 | $0.00007 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
Git Workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Workflow Skill
Cuándo usar esta skill
- Cuando necesites actualizar el CHANGELOG.md con nuevos cambios.
- Cuando vayas a hacer commit de cambios al repositorio.
- Cuando necesites hacer push de cambios al remoto.
- Cuando prepares una nueva release.
Convenciones de Commits
Este proyecto usa Conventional Commits:
type(scope): description
Tipos válidos:
| Tipo | Uso |
|---|---|
feat |
Nueva funcionalidad |
fix |
Corrección de bugs |
docs |
Cambios en documentación |
style |
Formato (sin cambio de código) |
refactor |
Refactorización |
test |
Añadir/modificar tests |
chore |
Mantenimiento |
Ejemplos:
feat(semantic): add image caption indexing
fix(navigation): resolve path validation error
docs: update tool reference with new parameters
Flujo de Trabajo Completo
1. Verificar estado actual
# Ver estado de archivos
git status
# Ver historial reciente
git log --oneline -10
2. Actualizar CHANGELOG.md
Formato requerido (Keep a Changelog):
## [Unreleased]
### Added
- Nueva feature X que hace Y.
### Changed
- Modificación en Z.
### Fixed
- Corrección del bug en W.
Secciones válidas: Added, Changed, Deprecated, Removed, Fixed, Security
3. Realizar commit
# Añadir todos los cambios
git add .
# Commit con mensaje convencional
git commit -m "type(scope): descripción"
Trailers especiales:
- Para bugs reportados:
git commit --trailer "Reported-by:<name>" - Para issues:
git commit --trailer "Github-Issue:#<number>"
⚠️ NUNCA incluir
Co-Authored-Byen los commits.
4. Push al remoto
git push origin main
Proceso de Release
Para crear una nueva versión:
1. Mover cambios de Unreleased a una versión
## [1.2.0] - 2026-01-20
### Added
- (mover items de Unreleased)
2. Actualizar versión en pyproject.toml
[project]
version = "1.2.0"
3. Commit de release
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 151 lines · 33 tokens per session scan A 6fb952b01246
Git Workflow is a skill published in the GitHub repository Vasallo94/obsidian-mcp-server (11 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 804 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
meeting-todos
Use when the user says /meeting-todos, "the meeting is done", "I just had a meeting", "pull the action items", "what did I commit to", or otherwise wants action items from a recent meeting note captured on their to-do list. Also when a meeting note or transcript needs its tasks pulled out. NOT for general task…