jeanjerome

495 — Git skill for Claude Code

Git community

An agent harness that carries a change from an intent to a branch you can merge — specified, produced in isolation, verified by your project's own commands, reviewed independently, accepted on evidenc.

How to install 495

This entry records only its repository, not the path inside it, so there is no exact command to give. Open jeanjerome/495 and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What 495 does

Alternatives in Git

Prime Isolation: Worktree Isolation And Git Ops Orientation — Prime Isolation: Worktree Isolation and Git Ops Orientation skill 17.6k ★
Triage Issues — Triage open GitHub issues — split into bugs vs features, rank by severity/opportunity, and flag under-specifie 12.6k ★
Container Use — by dagger - Development environments for coding agents 3.6k ★

README

The agent harness that ensures quality

[![License: Apache 2.0](https://img.shields.io/badge/License-Apache%202.0-blue)](LICENSE) [![Runtime: Python 3.11+](https://img.shields.io/badge/Runtime-Python%203.11%2B-blue)](https://www.python.org/) [![Agent: Claude Code](https://img.shields.io/badge/Agent-Claude%20Code-green)](https://www.anthropic.com/claude-code) [![Agent: Codex](https://img.shields.io/badge/Agent-Codex-green)](https://openai.com/codex/) [![Agent: Local models](https://img.shields.io/badge/Agent-Local%20models-green)](https://github.com/ollama/ollama) ![Status: Early](https://img.shields.io/badge/Status-Early-orange)

**495 is an *agentic engineering harness*: a control plane that carries a software change from an intent to a branch you can merge.** You write the request in prose; 495 has it specified, produced in isolation, verified by your project's own commands and reviewed from independent perspectives, then concludes on the evidence it collected — and hands you a patch, a branch and a report.

Every requirement, decision, intervention and piece of evidence is explicit and traceable. A change is accepted only when the evidence supports it, never because the agent says it is done. Nothing reaches your working tree until you ask for it, and what you merged is checked against what was verified.

A run driven from the surface: an intent typed into it, the specification stopped for approval before anything is produced, then the change written in its own worktree, verified, reviewed, concluded, and the delivered branch merged and checked