git-workflow

Guidance for using Git, a version-control system that records code changes and supports branches and pull requests.

In plain words
What is it for?
It helps create focused commits, make and update branches, resolve conflicts, review changes, and prepare pull requests with clear explanations.
Why use it?
It reduces messy history, accidental changes, merge problems, and unsafe collaboration practices.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/aiming-lab/metaclaw/git-workflow
Any agent
npx skills add aiming-lab/MetaClaw --skill git-workflow
Clone the repo
git clone --depth 1 https://github.com/aiming-lab/MetaClaw

Made for: Claude Code, Codex.

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 213 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00041 $0.00213
Opus 5 $0.00020 $0.00106
Sonnet 5 $0.00008 $0.00043
Haiku 4.5 $0.00004 $0.00021

Measured 3d ago against content hash 2e7cc0f35006, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

memory_data/skills/git-workflow/SKILL.md · 24 lines

What it actually says

Git Workflow Best Practices

Commits:

  • Write commit messages in imperative mood: Add feature X, not Added feature X.
  • One logical change per commit. Do not bundle unrelated changes.
  • Stage specific files (git add <file>), not git add . blindly.

Branches:

  • Branch from the latest main/master: git checkout -b feature/my-change.
  • Keep branches short-lived; merge or rebase frequently.

Pull Requests:

  • Include a short description of why, not just what.
  • Reference related issues (Closes #123).
  • Keep PRs focused — one feature or fix per PR.

Never: force-push to shared branches, skip hooks with --no-verify, or commit secrets.

Changes

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.

  1. 3d ago First seen · 24 lines · 41 tokens per session scan A 2e7cc0f35006

Subscribe to this mod's changes

git-workflow is a skill published in the GitHub repository aiming-lab/MetaClaw (3,494 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 213 once invoked, about $0.0002 per session on Opus 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-30.

Related

Other skills, from other repositories

design-taste-frontend

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

Leonxlnx/taste-skill · 61 tokens

stitch-design-taste

Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.

Leonxlnx/taste-skill · 50 tokens

full-output-enforcement

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

Leonxlnx/taste-skill · 44 tokens

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…

Leonxlnx/taste-skill · 116 tokens

imagegen-frontend-mobile

Elite mobile app image-generation skill for creating premium, app-native screen concepts and flows. Designed for iOS, Android, and cross-platform mobile products. Prioritizes clean hierarchy, comfortably readable text, strong multi-screen consistency, controlled color palettes, non-generic creative direction, textured…

Leonxlnx/taste-skill · 126 tokens

imagegen-frontend-web

Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not…

Leonxlnx/taste-skill · 126 tokens