Menu
Writes Git commit messages. Activates when the user asks to write a commit message, draft a commit message, or similar.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | writing-commit-messages |
| description | Writes Git commit messages. Activates when the user asks to write a commit message, draft a commit message, or similar. |
Write commit messages that follow commit style guidelines for the project.
<subsystem>: <summary>
<reference issues/PRs/etc.>
<long form description>
terminal, vt, lib, config,
font). Determine this from the file paths in the diff. If
changes span the macOS app, use macos. For GTK, use gtk. For
build system, use build. Use nested subsystems with / when
helpful and exclusive (e.g., terminal/osc).#1234Write and edit in GOV.UK / GDS house style — plain English, active voice, front-loaded content, sentence case, and no bold or italics for emphasis. Use when writing or editing reports, research write-ups, guidance, documentation, summaries, or any prose where clarity and accessibility matter.
Use windows-rs owned handle patterns in Rust Win32 code. Use when reviewing, writing, or refactoring Rust code that owns Windows handles such as HANDLE, service handles, registry handles, tokens, files, IOCP handles, or volume handles; especially when code defines custom OwnedHandle wrappers, manually calls CloseHandle in Drop, imports std::os::windows raw-handle ownership traits for Win32 values, or needs guidance on the windows::core::Owned type.
Add tracing spans for Tracy profiling in Teamy-Studio. Use when instrumenting startup, windowing, rendering, terminal, async work, or other performance-sensitive code paths and deciding which spans should be always-on versus gated behind the tracy feature.
Assess whether a path-like or path-adjacent value is safe to persist in source code, docs, tests, plans, or committed notes. Use when deciding if a path, username, hostname, share name, dataset name, version clue, product code, or similar string should be written down or should require user confirmation first.
Use Teamy-specific local workflow tools and conventions to discover repos, shrink workspace scope, and preserve useful context without overloading editors or leaking machine-specific details. Use when deciding how to find relevant local projects, what to keep open in VS Code, and which tool is appropriate for Codex versus GitHub Copilot or other editor workflows.
Persist and summarize path-like references mentioned by the user. Use when a response includes Windows paths, Unix-style paths, home-relative paths, UNC paths, mount-like paths, or other filesystem-like strings that should be recorded in the project for later use.