agentleFS
Sign inStart free
jmolzjmolz/m0lz.01/.agents/skills/source-command-commit/SKILL.md

source-command-commit

Skill0 starsChanged 6 months agoMITView on GitHub

Create a standardized, detailed git commit

  • Reads credentials

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the user asks to run the migrated source command commit.

    line 8
  2. Distinctive:

    Add changed and new files relevant to the current work.

    line 30
  3. Very specific:

    If ANY AI context files were modified, add a Context: section:

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

source-command-commit

Use this skill when the user asks to run the migrated source command commit.

Command Template

Commit Changes

Your git log is long-term memory. Future agent sessions will read these commits to understand project history. Make them count.

Process

1. Review Changes

git status
git diff --stat HEAD
git diff HEAD
git ls-files --others --exclude-standard

2. Stage Relevant Files

Add changed and new files relevant to the current work.

Do NOT stage:

  • .env or credential files
  • Large binary files
  • Files unrelated to the current task
  • IDE config or OS files

3. Create Commit Message

Format:

tag(scope): concise description of WHAT changed

WHY this change was made. Include context that isn't obvious
from the diff — the reasoning, the alternatives considered,
the user impact.

[Optional: Context section for AI layer changes]
[Optional: Fixes #123, Closes #456]

Tags:

  • feat: — new capability or feature
  • fix: — bug fix
  • refactor: — code restructure, no behavior change
  • docs: — documentation only
  • test: — test additions or fixes
  • chore: — build, CI, tooling, dependency updates
  • perf: — performance improvement
  • style: — formatting, no logic change

Scope (optional): the primary area affected

feat(auth): add OAuth2 login flow
fix(api): handle null response from payment gateway
refactor(db): extract query builder into utility module

4. Include AI Layer Changes

If ANY AI context files were modified, add a Context: section:

feat(dashboard): add real-time analytics widget

Added WebSocket-based live metrics with 5-second refresh.
Chose recharts over d3 for consistency with existing charts.

Context:
- Updated AGENTS.md with WebSocket patterns
- Added .codex/rules/websocket.md for connection conventions
- Created .codex/docs/analytics-architecture.md

What counts as AI context changes:

  • AGENTS.md — global rules
  • .codex/rules/ — on-demand rules
  • .agents/skills/source-command- — slash commands
  • .codex/docs/ — reference documents
  • .codex/plans/ — implementation plans

5. Commit

git add <files>
git commit -m "message"

Why This Matters

  • Future /prime commands read git log to understand recent work
  • Standardized tags make history scannable
  • The WHY section prevents re-discovery of dead ends
  • Context section tracks AI layer evolution alongside code

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free