commit

Commit repository changes and persist session findings into .claude/rules/.

2|Updated Jun 7, 2022
One-click install
npx skills add https://github.com/SebasAren/dotfiles --skill commit-sebasaren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/SebasAren/dotfiles/tree/main/pi/.pi/agent/skills/commit
Command: npx skills add https://github.com/SebasAren/dotfiles --skill commit-sebasaren

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps capture session discoveries, persist concise project rules, and produce a clean, conventional commit so knowledge is retained and repository state is recorded reliably.

Core Features & Use Cases

  • Session reflection: Guides the agent to review recent actions, surface gotchas, and identify misleading documentation or recurring pitfalls.
  • Rule management: Reads existing .claude/rules/, decides whether to append to an existing rule or create a new concise rule file with optional globs, and follows guidelines to avoid rule sprawl.
  • Safe committing: Stages changes, runs configured pre-commit hooks via wt step commit, and creates a conventional commit message while allowing selective staging when unrelated edits must be excluded.
  • Use case: After a refactor, summarize noteworthy findings, persist relevant rules, and commit the changes so future sessions inherit project knowledge.

Quick Start

Reflect on recent edits, optionally persist notable findings to .claude/rules/, and run wt step commit --yes to stage, lint, and commit the changes.

Frequently Asked Questions about commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit and save session findings to project rules?

To automate git commit and save session findings, this Skill stages changes, persists concise project rules to .claude/rules/, and runs wt step commit --yes to create a conventional commit while retaining repository knowledge.

How does session reflection work when committing repository changes?

Session reflection works by guiding the agent to review recent edits, surface gotchas, and identify misleading documentation or recurring pitfalls before staging and committing repository changes cleanly.

What's the best way to avoid rule sprawl when persisting project rules?

To avoid rule sprawl when persisting project rules, this Skill reads existing .claude/rules/ files and decides whether to append to an existing rule or create a new concise rule file with optional globs.

Can I selectively stage changes and exclude unrelated edits before running pre-commit hooks?

Yes, you can selectively stage changes to exclude unrelated edits before the Skill runs configured pre-commit hooks via wt step commit and creates a conventional commit message.

What do I need to run wt step commit and persist findings to .claude/rules/?

You need repository write access, a writable .claude/rules/ directory, the questionnaire tool for interactive selection, and the wt step commit command usable with the --yes flag.

Why are my conventional commits missing important session discoveries and gotchas?

Conventional commits miss session discoveries when findings are not persisted. This Skill captures gotchas by reflecting on recent actions and writing concise rules to .claude/rules/ before committing.