miaodi/commit-message
skills/commit-message/SKILL.md
Use when drafting, reviewing, or normalizing Git commit messages or Perforce changelist descriptions from the shared Git/P4 commit message template.
tools
Updated May 26, 2026
$ install --global
skillsauthnpx skillsauth add miaodi/llm_config commit-messageInstall 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: May 26, 2026, 4:32 AM48.9s1 file scanned
SKILL.md
- name:
- commit-message
- description:
- Use when drafting, reviewing, or normalizing Git commit messages or Perforce changelist descriptions from the shared Git/P4 commit message template.
Commit Message Skill
Purpose
Draft concise, reviewable commit messages and P4 changelist descriptions from the shared template.
Shared Template
Before drafting a message, identify which product is running this skill:
- Codex: use the Codex paths only.
- Copilot: use the Copilot paths only.
- OpenCode: use the OpenCode paths only.
Do not search every product's install location. Product-specific lookup keeps the template selection predictable and avoids unnecessary filesystem scans.
After identifying the product, read the first available template path for that product:
Codex
.codex/templates/commit-message/git-p4-commit-message-template.txtin the current repository root.${CODEX_HOME:-${HOME}/.codex}/templates/commit-message/git-p4-commit-message-template.txt.
Copilot
.github/templates/commit-message/git-p4-commit-message-template.txtin the current repository root.${HOME}/.vscode-server/data/User/templates/commit-message/git-p4-commit-message-template.txtwhen that VS Code server user directory exists.${HOME}/.config/Code/User/templates/commit-message/git-p4-commit-message-template.txt.
OpenCode
.opencode/templates/commit-message/git-p4-commit-message-template.txtin the current repository root.${OPENCODE_HOME:-${HOME}/.config/opencode}/templates/commit-message/git-p4-commit-message-template.txt.
If the product cannot be determined from the active agent environment, ask the user which product is invoking the skill instead of searching all product paths.
When working directly from this llm-config source checkout, the source template
at templates/commit-message/git-p4-commit-message-template.txt may be used as
the repository-local template.
Use that file as the single source of truth for message shape and allowed sections.
Rules
- For Git, produce the final message without template comments or placeholder text.
- For P4, require an actual STARs ID. If the user did not provide one and it cannot be found in the change context, ask for it before producing the final changelist description.
- For P4, produce the final changelist description without template comments, placeholder text, or synthetic separator lines, and append
STARs: <id>as the final line. - Use
type(scope): summarywhen there is a clear scope; usetype: summarywhen there is not. - Prefer concise summaries under 72 characters.
- Include a body only when it adds useful context beyond the summary.
- Include validation only when the user provides it or the workflow explicitly needs it; do not add placeholder validation.
- Preserve issue IDs, review IDs, STARs IDs, or breaking-change footers when provided by the user or discovered in the change context.
Output
Provide the commit message or changelist description ready to paste or submit.
Related Skills
miaodi/computational-learning-notes
development
VerifiedTrustedCommunity
Use when creating C++ learning notes or minimal experiments for low-level computational, numerical, CPU/GPU, compiler, and hardware concepts such as false sharing, floating point, registers, caches, SIMD, atomics, numerical stability, and benchmarking pitfalls.
SKILL.mdUpdated Jun 2, 2026
miaodi/latex-project-build
development
VerifiedTrustedCommunity
Use when configuring, diagnosing, or compiling LaTeX projects, especially multi-file reports, theses, books, chapter-based projects, Overleaf exports, latexmk/arara/Makefile workflows, bibliography/index/glossary passes, or projects that require pdflatex, xelatex, lualatex, latex->dvips, biber, or bibtex.
SKILL.mdUpdated May 28, 2026
miaodi/graph-algorithms
development
VerifiedTrustedCommunity
Use when working with graph traversals (BFS, DFS, level-order), minimum spanning trees, strongly connected components, topological sort, graph coloring, bipartite detection, elimination trees, level-set extraction, parallel graph algorithms, task-tree parallelism, sparse graph representations, and exploiting graph structure for parallel sparse computations.
SKILL.mdUpdated May 21, 2026
miaodi/git-workflow
testing
VerifiedTrustedCommunity
Use when planning or executing Git branch workflows, especially merge/rebase across branches, conflict resolution, safe history rewriting, and recovery from mistakes.
SKILL.mdUpdated May 21, 2026