gastown: Skill for Claude Code

.claude/skills/crew-commit/SKILL.md

crew-commit is a skill for Claude Code from gastownhall/gastown. It costs 43 tokens per session (1,448 once invoked), scanned A, original, MIT.

A step-by-step Git workflow for Gas Town crew members. Git is a system for tracking code changes, while a pull request is a proposed change submitted for review.

In plain words
What is it for?
Use it when finished work needs to be committed, pushed to a remote repository, and submitted for review.
Why use it?
It helps contributors avoid changing the main branch directly and provides an ordered process for checking work, creating a branch, committing, pushing, and opening a pull request.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

This is gastownhall/gastown's own configuration. It tells Claude Code how to work on gastown itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gastown configures →

About the project

Gas Town is a workspace manager for coordinating multiple AI coding agents across projects while preserving their work state in git-backed records. Developers use it to organize agents, tasks, identities, mailboxes, and handoffs across repositories. Its catalogue add-ons support operating and coordinating Gas Town workflows.

gastownhall/gastown · 18,711 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to gastownhall/gastown. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/gastownhall/gastown/main/.claude/skills/crew-commit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/gastownhall/gastown

Made for: Claude Code.

Wrote 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.

agentmods badge for crew-commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/gastownhall/gastown/crew-commit/github.svg)](https://agentmods.dev/skills/gastownhall/gastown/crew-commit)
Your own site
<a href="https://agentmods.dev/skills/gastownhall/gastown/crew-commit"><img src="https://agentmods.dev/badge/skills/gastownhall/gastown/crew-commit/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.

agentmods 80×15 button for crew-commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/gastownhall/gastown/crew-commit"><img src="https://agentmods.dev/badge/skills/gastownhall/gastown/crew-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,448 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 225
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
How audits are shown
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.1 $0.00043 $0.01448
Opus 5.5 $0.00017 $0.00579
Sonnet 5.5 $0.00009 $0.00290
Haiku 4.5 $0.00004 $0.00145

Measured 2mo ago against content hash 213018107984, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

crew-commit 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.

.claude/skills/crew-commit/SKILL.md · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Crew Commit — Canonical Git Workflow

This skill guides crew members through the standard Gas Town commit workflow: pre-flight → branch → stage → commit → push → PR.

⚠️ NEVER commit directly to main. All crew work goes through branches and pull requests. The Refinery handles merges to main.

Usage

/crew-commit

Run this when you have changes ready to commit. The skill walks you through each step in order.


Step 1: Pre-flight Checks

Before touching anything, sync with origin and verify your state.

# Fetch latest from origin
git fetch origin

# Check current branch and status
git status
git branch --show-current

# If you're on main, STOP — create a branch first (Step 2)

If you're behind origin/main, rebase now:

git rebase origin/main

If there are conflicts, resolve them carefully before proceeding. If stuck on a rebase conflict, stop and get help rather than force-pushing.


Step 2: Create a Feature Branch

If you're already on a feature branch, skip to Step 3.

Branch naming convention: <type>/<short-description>

Types:

  • feat/ — new feature
  • fix/ — bug fix
  • refactor/ — code restructuring
  • docs/ — documentation only
  • chore/ — maintenance, deps, config
  • test/ — tests only
# Create and switch to feature branch
git checkout -b feat/my-feature-description

# Or use the crew/<name> prefix for crew-specific branches
git checkout -b crew/<your-name>/description

Step 3: Submodule Warning

Check for submodules before staging. Accidentally committing a submodule pointer change causes cascading failures for other crew members.

# Check if repo has submodules
cat .gitmodules 2>/dev/null || echo "(no submodules)"

# Check for dirty submodule state
git submodule status 2>/dev/null

Common submodule paths to watch: shared/, config/, vendor/

If you see changes in submodule directories:

  • Do NOT git add shared/ or git add config/ unless you intentionally bumped the submodule pointer
  • Submodule pointer changes should be explicit and deliberate
  • When in doubt, ask before including submodule changes

Read the full file on GitHub · 235 lines

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. 2mo ago First seen · 235 lines · 43 tokens per session scan A 213018107984

Subscribe to this mod's changes

crew-commit is a skill published in the GitHub repository gastownhall/gastown (18,711 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 1,448 once invoked, about $0.0002 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-30.

Related

crew-commit compared with skills from other repositories

crew-commit next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
crew-commitgastownhall/gastownSkill19k9d agoMITA43Claude Code
github-automationruvnet/rufloSkill81ktodayMITA61Claude Code
changelogDonchitos/Claude-Code-Game-StudiosSkill36k18d agoMITA22Claude Code
comet-safe-deliveryrpamis/cometSkill3.3ktodayMITA78Claude Code, Codex
coco-shipcoco-research/cocoSkill785yesterdayApache-2.0A69Claude Code
close-task-commit-push-prdevoxx/DevoxxGenieIDEAPluginSkill687yesterdayMITA64Claude Code
git-workflowjezweb/claude-skillsSkill1.1k28d agoMITA52Claude Code