jimweller/commit
configs/claude-code/skills/commit/SKILL.md
Create an atomic conventional commit with AI context tracking
data-ai
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add jimweller/dotfiles commitInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 12:59 PM54.8s1 file scanned
SKILL.md
- name:
- commit
- description:
- Create an atomic conventional commit with AI context tracking
<!-- markdownlint-disable-file MD041 -->
STARTER_CHARACTER = 📌
Commit Changes
Process
1. Review Changes
git status
git diff HEAD
git diff --stat HEAD
```text
Check for new untracked files:
```bash
git ls-files --others --exclude-standard
```text
### 2. Stage Files
Add the untracked and changed files relevant to the current work.
**Do NOT stage:**
- `.env` or credential files
- Large binary files
- Files unrelated to the current task
### 3. Create Commit
Write an atomic commit message with a conventional commit tag:
- `feat:` -- New capability or feature
- `fix:` -- Bug fix
- `refactor:` -- Code restructure without behavior change
- `docs:` -- Documentation only
- `test:` -- Test additions or fixes
- `chore:` -- Build, CI, tooling changes
- `perf:` -- Performance improvement
**For monorepo changes spanning multiple packages**, note the primary package in the scope:
```text
feat(workflows): add DAG condition evaluator
fix(web): resolve SSE reconnection on navigation
refactor(isolation): simplify worktree resolution order
```text
**Commit message format:**
```text
tag(scope): concise description of what changed
[Optional body explaining WHY this change was made,
not just what changed. Include context changes that aren't
obvious from the diff.]
[Optional: Fixes #123, Closes #456]
```text
### 4. Capture AI Context Changes
If any AI context assets were modified in this commit, add a `Context:` section to the commit body:
```text
feat(orchestrator): add retry logic for session recovery
Added exponential backoff when SDK subprocess crashes mid-session.
Previously a single crash would fail the entire workflow.
Context:
- Updated .claude/rules/orchestrator.md with retry conventions
- Added .claude/commands/debug-session.md for session state inspection
- Surfaced issue: mock.module() in retry tests needs isolated batch
Fixes #482
```text
**What counts as AI context changes:**
- `.claude/rules/` -- on-demand conventions added, updated, or removed
- `.claude/commands/` -- slash commands created or modified
- `.claude/skills/` -- slash commands created or modified
- `.llmdocs/` -- reference docs added or updated
- `CLAUDE.md` -- global rules changes
- `**/CLAUDE.md` -- folder local rules changes
Git log is long-term memory for future sessions.
Related Skills
jimweller/transcript-search
testing
VerifiedTrustedCommunity
Search saved session transcripts for past decisions, actions, errors, and context that has left the current conversation window.
1SKILL.mdUpdated Apr 22, 2026
jimweller/prd-review
data-ai
VerifiedTrustedCommunity
Review a PRD for defects via Claude opus subagent.
SKILL.mdUpdated Apr 29, 2026
jimweller/md-syntax
development
VerifiedTrustedCommunity
Markdown authoring guidelines for formatting, code blocks, and structure. Use when writing or editing markdown files.
SKILL.mdUpdated Apr 29, 2026
jimweller/configs/claude-code/skills/md-style
development
VerifiedTrustedCommunity
--- name: md-style description: README style guide for concise, direct documentation. Use when writing or editing README files. ß--- <!-- markdownlint-disable-file MD041 --> # README Style Guide Write concise, direct README files for experienced engineers. ## Principles - **No fluff** - Skip tables of contents, verbose explanations, development history - **No roadmaps** - Document current state only, not plans or decisions. Readme is an engineering specification. Not a project plan or chan
SKILL.mdUpdated Apr 29, 2026