taylorhuston/local-life-manager · Archived

commit

Create git commits in spaces/[project]/ with conventional message format. Use for saving progress with quality checks and proper commit messages.

First seen Jan 26, 2026

Installation

$ npx skills add taylorhuston/local-life-manager --skill commit

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from taylorhuston/local-life-manager · top by installs.

npx skills add taylorhuston/local-life-manager

Browse all from taylorhuston/local-life-manager

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 69
License MIT
Default branch main
Open issues 1
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Glob, Grep, Bash
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,947 B
  • docs SUMMARY.md 159 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 12 installs

SKILL.md

/commit

Create git commits in spaces/[project]/ with quality checks and conventional message formatting.

Usage

/commit yourbench                     # Interactive commit
/commit yourbench "feat: add auth"    # Direct with message
/commit coordinatr --amend            # Amend last commit (safety checks)
/commit yourbench "fix: typo" --no-verify  # Skip hooks

Two Repos Involved

Meta-repo (ideas/):          spaces/yourbench/
├── ideas/yourbench/         ├── src/
│   ├── specs/               ├── tests/
│   └── issues/              └── .git/  <- Project git
├── .claude/
└── .git/  <- Meta-repo git

Auto-detect behavior:

  • Only spaces/[project]/ changed -> commit in project repo
  • Only ideas/ or meta-repo changed -> commit in meta-repo
  • Both changed -> ask: "Commit to both repos? (project/meta/both)"

Execution Flow

1. Detect Changes

# Check meta-repo
git status --porcelain ideas/ .claude/ shared/ resources/

# Check project repo
git -C spaces/[project] status --porcelain

2. Run Quality Checks (unless --no-verify)

npm test  # or pytest, cargo test, etc.
npm run lint

3. Review Changes

git status
git diff --staged

4. Generate Commit Message

Conventional commit format:

type(scope): description

[optional body]

Co-Authored-By: Claude <[email protected]>

Types:

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation
  • refactor: Code refactoring
  • test: Adding/updating tests
  • chore: Maintenance

Auto-detect type from changes:

  • New files in src/ -> feat
  • Changes to existing behavior -> fix or refactor
  • Only test files -> test
  • Only docs -> docs

5. Link to Issue (if applicable)

If on feature branch like feature/001-auth:

feat(001): implement user authentication

Refs: TASK-001

6. Execute Commit

cd spaces/yourbench
git add .
git commit -m "message..."

Amend Mode

Safety checks before amending:

  1. Not pushed to remote: git log @{u}..HEAD
  2. You're the author: git log -1 --format='%ae'

Branch-Aware Messages

Branch Commit Type
feature/001-auth feat(001): ...
bugfix/002-login fix(002): ...
main / develop No issue reference

Error Handling

Error Resolution
Project not found Check spaces/[project]/ exists
Not a git repo Run git init in project
Tests failing Fix tests before committing
Nothing to commit No staged/unstaged changes
Amend pushed commit Cannot amend, create new commit