claude

pyhouse-git

Repository workflow, independent of language and of any architecture. Ships the git-commit-message skill, which carries the Conventional Commits 1.0.0 convention an agent follows whenever it writes a commit message — a type that records the release the change earns, feat for a minor, fix for a patch, a break for a major, or for a minor below 1.0.0, so a version is read off the history instead of argued at release time. Also the git-branching skill — one mainline, one merge method recorded per repository, short-lived branches whose history is cleaned before it lands and never rewritten after. Then /pyhouse-git:adopt, which records in a repository's agent instructions how its changes branch, land and are committed and turns off the agent's own authorship line, /commit, which stages the named files, reviews the staged diff and commits only those files by git-commit-message, and /install-commit-hook, which puts a commit-msg hook in the repository so a malformed message is refused at commit time, and /release, which proposes the next version from the commit types since the last tag and cuts it only on an explicit yes. And /release-notes, which drafts the release note for the project's users from the changes themselves, never from the commit subjects. Depends on nothing and is installed on its own.

3 on GitHubby Yegor Vorobyevv0.10.1MITupdated 2 days ago
/

Plugin pyhouse-git from marketplace pyhouse in wntic/pyhouse. Commands read from the repo's manifest — 2 days ago.

What it installs

Skills (2)

  • git-branching

    Use when starting a branch, deciding how a change reaches the mainline, cleaning a branch's history before it lands, or choosing whether a repository needs more than one long-lived branch — in a repository of any language. Owns the one mainline releases are cut from, recording the branching and merg

  • git-commit-message

    Use when writing a commit message or a merge or pull request's title or description, or deciding what type, scope or breaking-change marker a change takes — whether through a command or typed by hand, in a repository of any language. Owns the Conventional Commits 1.0.0 message shape, the rule that t

Slash commands (5)

  • /pyhouse-git:adopt

    Write into this repository's CLAUDE.md how changes branch, land and are committed, and turn off the agent's own authorship line, so agents use the git skills rather than merely having them installed

  • /pyhouse-git:commit

    Stage the named files and commit them with a Conventional Commits 1.0.0 message whose type states what the change earns — a feature, a fix, or a break

  • /pyhouse-git:install-commit-hook

    Install the commit-msg hook that rejects a commit message which is not Conventional Commits, either shared with the repository or local to this clone

  • /pyhouse-git:release-notes

    Draft the release note for a release, or for what is not released yet — what changed for the people who use the project, what a break asks of them, what is deprecated — written from the changes themselves, for the person to approve

  • /pyhouse-git:release

    Propose the next version from the commits since the last tag — per member, where a repository versions several independently — and only on an explicit yes write the one release commit and tag it

View source on GitHub

More from wntic/pyhouse

All 6 plugins →

Python house-style rules that bind whichever architecture a service uses: naming derivation, typing and logging forms, the package and re-export contract, settings read from the environment, the data-access obligations every store meets, what a program owes a unit delivered at least once, the lint, type-check and dependency configuration every distribution carries once, the single error catalogue, what a distribution's version promises and which change moves it, the testing constitution, the workspace root for a repository holding several distributions, the container image a runnable program ships in, and a command-line interface's commands, exit codes and their test. Ships the hex-vs-flat architecture chooser and its /choose-architecture command, so a greenfield service can settle its family before installing pyhouse-hex or pyhouse-flat, the /pyhouse-universal:adopt command, which tells a repository's agents which skill governs each kind of Python work, and the namespaced /pyhouse-universal:code-review command with the reviewer subagent behind it, which applies these skills to existing code instead of writing new code, and the /pyhouse-universal:change-review command with the change-reviewer subagent behind it, which reviews a change before it lands for the contracts it breaks, the failure paths nothing catches and the tests that would not notice, each finding with the scenario that goes wrong.

18 skills · 4 commands · 2 agents

3

Hexagonal (ports-and-adapters) Python service skills: layer boundaries and the composition root, entities and value objects, repository and capability ports, CQRS commands, queries and handlers, relational persistence with paired migrations, dishka wiring, the FastAPI REST family with optional token auth, and the eight test families that cover them. Depends on pyhouse-universal, which Claude Code installs with it.

23 skills

3

Flat package-by-technical-role Python service skills for workers, crawlers, pipelines, ETL and glue, written for one distribution on its own and equally true of one among several: the one-time project setup — the dependencies each role brings and the migration bootstrap — the four role kinds and the import contract between them, one data-access package per store, named for its technology and the obligations that come with it, entrypoint trigger choice between loop, schedule, stream, HTTP and durable execution, and the four test families that cover them. Depends on pyhouse-universal, which Claude Code installs with it.

8 skills

3

How one change is delivered, rather than how its code is written. Ships the delivery-spec skill — the spec a change is implemented from, short enough to review in one sitting, naming as contracts only what other code depends on and stating the behaviour its tests are written from, its statements about today's system checked before any code exists, and its goal, scope and contracts frozen once it is ready. And /pyhouse-delivery:spec, which writes that spec with the person who wants the change, checks those statements and marks the spec ready once the person has accepted it. Ships delivery-change-contract — the short list of what is frozen while a ready spec is implemented, and every edit to it caught by a diff from a base commit rather than forbidden. And /pyhouse-delivery:implement, which implements a ready spec through the delivery-implementer subagent, which writes the tests from the spec before the code, then the code, and checks its own work by the project's gate and, where the change shows only in a running process, a live check — then /pyhouse-universal:change-review and one round of fixes — and hands over the body of the merge commit. Depends on pyhouse-universal.

2 skills · 2 commands · 1 agent

3

pyhouse

claude

The whole pyhouse catalogue in one install: depends on pyhouse-universal, pyhouse-hex, pyhouse-flat, pyhouse-git and pyhouse-delivery, which Claude Code installs with it, and ships /pyhouse:setup, which sets a repository up for them in one run — the Python skill table and the branching section in its CLAUDE.md, the agent's authorship line turned off, and the commit-msg hook — by running each plugin's own commands in turn. Holds no skill and states no rule of its own.

1 command

3

Similar plugins

Commands for git commit workflows including commit, push, and PR creation

3 commands

anthropics/claude-code 155,476

agentic-flow (external: maintained in ruvnet/agentic-flow, pinned to commit d19737b, plugin 3.4.0): the agentic-flow MCP server pinned to [email protected] (ReasoningBank learning, ecosystem tools prompt_injection_scan, swarm_partition_tasks, sublinear_solve, sublinear_pagerank and ecosystem_status, multi-provider routing, autopilot learning; readonly profile by default, no tool pre-approved), 2 agents, 4 skills, /agentic-flow-status, and a mod guard on agentic_flow_agent with /agentic-flow-guard

4 skills · 1 command · 2 agents · 1 MCP server

ruvnet/ruflo 81,589

Perform AI code review on Git diffs — supports workspace changes, branch ranges, and single commits with concurrent per-file analysis, codebase search, and deep context-aware review.

2 commands

alibaba/open-code-review 50,068

Portfolio monitoring and analytics for private-capital LP teams using the Chronograph connector: cashflow forecasting, commitment pacing, look-through exposure scans and GP-meeting prep. Requires a Chronograph account and the Chronograph connector.

4 skills · 5 agents

anthropics/claude-plugins-official 47,076

Essential developer skills including Git workflows, SQL optimization, error handling, code review, E2E testing, authentication, debugging, and monorepo management

11 skills · 1 agent

wshobson/agents 42,461

Portfolio monitoring and analytics for private-capital LP teams using the Chronograph connector: cashflow forecasting, commitment pacing, look-through exposure scans and GP-meeting prep. Requires a Chronograph account and the Chronograph connector.

4 skills · 5 agents

anthropics/knowledge-work-plugins 35,601

Maintain pyhouse-git?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins6 plugins