jitsusama/git-commit-convention
skills/git-commit-convention/SKILL.md
Operational commit rules: when to commit, what goes in each commit, commit frequency and history management. Use when committing code, deciding commit boundaries or managing git history. Pairs with commit-format for message structure.
$ install --global
skillsauthnpx skillsauth add jitsusama/agentic-harness.pi git-commit-conventionInstall 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 16, 2026, 6:52 AM5.4s2 files scanned
SKILL.md
- name:
- git-commit-convention
- description:
- >
- Operational commit rules:
- when to commit, what goes in
Git Commit Convention
For the commit message format itself (conventional commits,
types, scopes, subject and body rules), see commit-format.
This skill covers the operational conventions: when to commit,
what goes in each commit, and how to manage history.
Commit Frequency
- Commit after each logical unit of work.
- In TDD: commit after each green + refactor cycle.
- When planning: commit the plan file itself.
- Don't batch unrelated changes into one commit.
Atomic Commits
Each commit should be one concern:
- One bug fix per commit.
- One feature step per commit.
- One refactor per commit.
- Tests and implementation in the same commit (they're one unit).
If you find yourself writing "and" in the subject line, it's probably two commits.
History
- Interactive rebase is fine for cleaning local history before push.
- Never force-push shared branches without discussion.
- Prefer
--force-with-leaseover--forcewhen rewriting remote. - Never use
--amend. Make a new commit instead. Amending rewrites history and is almost never worth it. A new commit is cleaner and preserves the work trail. If the previous commit has a mistake, fix it forward with a new commit. - Avoid WIP commits on shared branches; squash locally with interactive rebase before pushing.
When Not to Commit
- Broken tests (unless explicitly spiking or experimenting).
- Half-finished features without a clear stopping point.
- Generated files that should be in .gitignore.
Related Skills
jitsusama/quest-format
development
VerifiedTrustedCommunity
Structure of a quest README and the documents that live under it: frontmatter shape, the four core and four optional body sections, emoji glyphs, ID format, alias notation, Cast bullets and Journey entries. Use when writing or editing a quest README, a plan, research, brief or report document under a quest. Pairs with quest-convention for choices like kind, promotion and reordering. Follow the prose-standard for voice.
5SKILL.mdUpdated Jun 4, 2026
jitsusama/quest-convention
tools
VerifiedTrustedCommunity
Operational conventions for the quest system: when to use a quest versus a subquest versus a sidequest, when to scaffold a plan or research document, how to reorder priorities, when to add optional sections, when to conclude versus retire, the resuscitate pattern. Use when driving the quest tool, deciding kind, promoting or parking work, or organising a project as quests. Pairs with quest-format for the on-disk shape.
5SKILL.mdUpdated Jun 4, 2026
jitsusama/markdown-standard
development
VerifiedTrustedCommunity
Markdown structure rules: Title Case headings with their exceptions, the line-width target and its legitimate exceptions, reference-style links, fenced code blocks with language tags, tables and lists. Use when writing or editing any markdown file (README, AGENTS, docs, plans, skill files), or when adding a heading, link, table or code block. Owns markdown structure; pairs with prose-standard, which owns voice, grammar, spelling and punctuation.
5SKILL.mdUpdated Jun 4, 2026
jitsusama/convention-recurrence-sensor-guide
tools
VerifiedTrustedCommunity
How to measure whether convention corrections keep recurring in the pi session logs, by category and by week. Use to record a baseline before the convention gates take effect and to re-run afterwards to confirm the recurring categories bend down. Pairs with the convention gates (pr-guardian, issue-guardian, commit-guardian, slack-integration) and the convention-context extension.
5SKILL.mdUpdated Jun 4, 2026