commit-message
Skill2.3k starsChanged 4 days agoBSD-3-ClauseView on GitHub
Use when writing any commit message, PR description, or attempting to push to GitHub. This contains important guidelines for writing commit and PR messages. Invoke upon any request to write a good PR or commit message, summarize work in a commit message, squash commits into a combined message, or to edit, simplify, or improve a commit message.
75 other projects use a version of this.
Trending
Steady talk.about the whole repository
Most recently taken up by
- Eclipter/agentstheir own version, first seen Nov 16, 2026
- travissmithv1/claude-skillstheir own version, first seen Nov 16, 2026
- antick/skillstheir own version, first seen Nov 16, 2026
- beecode-rs/claude-skillstheir own version, first seen Nov 16, 2026
- Citxen/Claude-Skillstheir own version, first seen Nov 16, 2026
- michagrandel/skillstheir own version, first seen Nov 16, 2026
Who's talking about AcademySoftwareFoundation/OpenShadingLanguage
- A Hacker News story“Open Shading Language – Advanced shading language for production GI renderers”Hacker News · Aug 23, 2021 · 54 points
- github-linguist/linguist“Open Shading Language”GitHub · Jan 19, 2025 · 2 reactions
- appleseedhq/appleseed“Osl update to 1.13”GitHub · Jul 29, 2025 · 1 reactions
- GafferHQ/dependencies“Update OpenImageIO, OSL, Cycles and others”GitHub · Jun 3, 2025 · 1 reactions
- AcademySoftwareFoundation/OpenImageIO“ci: cache the dependencies that Windows CI builds from source”GitHub · Oct 26, 2026
The biggest 5 of 38 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 38
Talked about on GitHub and Hacker News (38 times).
On GitHub · 37
- Jan 19, 2025Open Shading Language — github-linguist/linguist2 reactions
- Jul 29, 2025Osl update to 1.13 — appleseedhq/appleseed1 reaction
- Jun 3, 2025Update OpenImageIO, OSL, Cycles and others — GafferHQ/dependencies1 reaction · 2 comments
- Oct 26, 2026ci: cache the dependencies that Windows CI builds from source — AcademySoftwareFoundation/OpenImageIO0 reactions · 1 comment
- Aug 3, 2026openshadinglanguage: 1.15.5.0 -> 1.15.6.0 — NixOS/nixpkgs0 reactions · 3 comments
32 more on GitHub
- May 20, 2026OCIO 2.3.2 doesn't build in 2023.3 image due to invalid hex constant in mz.h — AcademySoftwareFoundation/aswf-docker0 reactions · 3 comments
- May 6, 2026openshadinglanguage: 1.15.3.0 -> 1.15.5.0 — NixOS/nixpkgs0 reactions · 3 comments
- Mar 10, 2026openshadinglanguage: 1.15.1.0 -> 1.15.3.0 — NixOS/nixpkgs0 reactions · 1 comment
- Dec 2, 2025osl: 1.14.7.0 -> 1.15.1.0 — NixOS/nixpkgs0 reactions · 2 comments
- Nov 14, 2025Encountered a shader codegen related exception for the following node: ND_surfacematerial, ND_geompropvalueuniform_filename, ND_blur_float, ND_blur_color3, etc. — AcademySoftwareFoundation/MaterialX0 reactions · 6 comments
- Nov 10, 2025MaterialXGenOsl_LibsToOso: Unable to generate OSL shaders with ND prefix — AcademySoftwareFoundation/MaterialX0 reactions · 4 comments
- Aug 8, 2025osl: 1.14.6.0 -> 1.14.7.0 — NixOS/nixpkgs0 reactions
- Jul 3, 2025osl: 1.14.5.1 -> 1.14.6.0 — NixOS/nixpkgs0 reactions
- Feb 21, 2025Integrating matrix multiplication fix from OSL — AcademySoftwareFoundation/OpenColorIO0 reactions · 1 comment
- Jan 3, 2025Reference geometric normal in `mx_forward_facing_normal` — AcademySoftwareFoundation/MaterialX0 reactions
- Oct 10, 2024Undefined behavior in Vec::operator[] — AcademySoftwareFoundation/Imath0 reactions · 8 comments
- Sep 14, 2024osl: 1.13.10.0 -> 1.13.11.0 — NixOS/nixpkgs0 reactions
- Aug 21, 2024Align smoothstep edge cases with OSL — AcademySoftwareFoundation/MaterialX0 reactions
- Jun 11, 2024Dev Days 2024 Project Application - Open Shading Language — AcademySoftwareFoundation/tac0 reactions · 1 comment
- Jun 3, 2024osl: 1.13.9.0 -> 1.13.10.0 — NixOS/nixpkgs0 reactions
- May 2, 2024osl: 1.13.8.0 -> 1.13.9.0 — NixOS/nixpkgs0 reactions
- Apr 4, 2024ArnoldTextureBackTest : Hack around OSL bug — GafferHQ/gaffer0 reactions
- Apr 2, 2024osl: 1.13.7.0 -> 1.13.8.0 — NixOS/nixpkgs0 reactions
- Mar 2, 2024osl: 1.13.6.1 -> 1.13.7.0 — NixOS/nixpkgs0 reactions
- Feb 2, 2024osl: 1.12.14.0 -> 1.13.6.1 — NixOS/nixpkgs0 reactions
- Nov 20, 2023osl: fix build, 1.12.13.0 -> 1.12.14.0 — NixOS/nixpkgs0 reactions · 7 comments
- Nov 14, 2023[Bug][CI Image][osx] fatal error: 'wchar.h' file not found — microsoft/vcpkg0 reactions · 9 comments
- Oct 21, 2023Build failure: osl — NixOS/nixpkgs0 reactions · 3 comments
- Sep 7, 2023Intermittent crash in LLVM when used from OSL (Open Shading Language) in interactive use case (seemingly due to insufficient 32 bit relocation offsets?) — llvm/llvm-project0 reactions · 33 comments
- May 5, 2023osl: 1.12.11.0 -> 1.12.12.0 — NixOS/nixpkgs0 reactions
- Jan 19, 2023ShadingEngine : Prototype support for OSL SIMD — GafferHQ/gaffer0 reactions · 9 comments
- May 29, 2022Fix incorrect transform in genosl — AcademySoftwareFoundation/MaterialX0 reactions · 9 comments
- Dec 9, 2021Different translucent closure def in stdosl.h compared to OSL — AcademySoftwareFoundation/MaterialX0 reactions · 14 comments
- Nov 22, 2021OSLCode : Check for empty `.oso` files — GafferHQ/gaffer0 reactions · 1 comment
- Nov 5, 2021[New Port Request] Open Shading Language — microsoft/vcpkg0 reactions · 1 comment
- Jun 6, 2021Create an onboarding process/document — vfx-rs/openexr-bind0 reactions
- Mar 23, 2021Added initial draft for OSL closures — AcademySoftwareFoundation/MaterialX0 reactions · 4 comments
On Hacker News · 1
- Aug 23, 2021Open Shading Language – Advanced shading language for production GI renderers54 points · 8 comments
Used with
Projects with it also use pr-description, api-docs and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillpr-description
Draft Nacelle PR titles, pull request descriptions, commit titles, commit descriptions, and squash commit messages. Use when asked for PR or commit wording, a branch summary, or a PR description that can be used in a commit. Omit validation sections from commit bodies and remove filler.
Also in 12 projects that use this
LangChainSkillapi-docs
OpenAPI documentation and REST API design patterns
Also in 3 projects that use this
cryptofish7Skillsmoke-test
Generate and maintain a local deploy script (scripts/deploy.sh). Discovers project services, deploys them locally, and health-checks each one. Use when the user asks to "smoke test", "deploy locally", "test local deploy", "update deploy script", "run deploy", or "run smoke test".
Also in 3 projects that use this
srclightSkillrefactor-safely
This skill should be used when the user asks to "refactor", "rename", "move", "change a function signature", "extract a method", "delete unused code", "clean up", or any modification that could break callers or dependents. Provides a pre-change safety checklist using srclight's graph tools to assess blast radius before touching code.
Also in 3 projects that use this
HashiCorpSkillchangelog
Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 11 projects that use this
Other versions75 projects use a version of this.
Word for word · 1
- AcademySoftwareFoundation/OpenImageIO★ 2.4k100% same
Edited · 0
None found.
Wrote their own version · 74
- zulip/zulip★ 26ksame name
- mergisi/awesome-openclaw-agents★ 4.1ksame name
- AltraMayor/f3★ 3.4ksame name
- github/copilot-cli-for-beginners★ 2.9ksame name
- sheshbabu/zen★ 1.2ksame name
- s-kostyaev/ellama★ 963same name
- tektoncd/operator★ 612same name
- danielvm-git/bigpowers★ 292same name
- rshdhere/vibecheck★ 213same name
- mattiacerutti/supernova★ 196same name
64 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- check-dependency-minmaxSkill
- prepare-patch-releaseSkill
- release-notes-updateSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 63 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Every git commit in this project that uses agents must contain a line near the end of the expository section (but before any Signed-off-by …
- Distinctive: line 17
No exceptions. Ensure that there is one blank line after this attribution and before any subsequent non-blank line.
- Distinctive: line 19
Never say "Co-authored by" or anything that implies AI authorship.
- Distinctive: line 21
If the agent fully writes any part of the body of a commit message (beyond the first subject line), it should always preface the …
- Distinctive: line 31
Do not offer to remove the "AGENT says" line, but do remind the user that the entire message is agent written, that the project encourages …
- Distinctive: line 36
When this skill is invoked, let the user know by telling them: "Invoking the commit-message skill."
- Distinctive: line 62
If you are writing a commit where you think the work is mostly done and this will likely be the message that becomes the PR description, …
- Distinctive: line 66
If it's not clear which of these situations applies, ask the user if they are ready for you to (a) write the final submission commit …
- Distinctive: line 84
No em dashes, smart quotes, or decorative Unicode symbols.
“Common” is measured: kept by at least 6 in 10 of the 63 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Unbreakable rules
- Agents may never submit a PR or a PR comment and should refuse if asked to do so. In this project, only human users are allowed to directly submit or comment on PRs or issues.
- Every git commit in this project that uses agents must contain a line near
the end of the expository section (but before any Signed-off-by or
other human Co-authored-by) with the text
No exceptions. Ensure that there is one blank line after this attribution and before any subsequent non-blank line.Assisted-by: <TOOL-OR-HARNESS-NAME> / <MODEL-NAME> - Never say "Co-authored by" or anything that implies AI authorship. Only "Assisted-by".
- If the agent fully writes any part of the body of a commit message (beyond
the first subject line), it should always preface the agent-written section
with:
Do not offer to remove the "AGENT says" line, but do remind the user that the entire message is agent written, that the project encourages that they write their own commit messages when possible, and suggest that they edit it, put it into their own words as much as possible, and then they may remove the "AGENT says" notice.<FIRST SUBJECT LINE HERE> <AGENT> says: <rest of commit-written text goes here> - When this skill is invoked, let the user know by telling them: "Invoking the commit-message skill."
Types of commit messages: WIP commits versus submission commits
WIP commits : These are intermediate checkpoints of work in progress, not intended as the final message that will be submitted as a PR. These may be done autonomously by a long-running agentic workflow, to separate sequential steps of development, or to separate unrelated fixes into discrete commits, or at the user's request.
WIP commits may contain any detailed information deemed helpful by the agent, so that subsequent tasks or sessions can understand the work done so far and resume the work. They may use advice in the guidelines below when it is helpful, but need not consider it mandatory if there are other goals or priorities that necessitate breaking those guidelines. (But they still must follow the "unbreakable rules" above.)
Submission commits : The final message of the sole (or squashed) commit that will be submitted as a PR, and thus will by default become the PR's description (plus further editing that the PR's human committer may do).
Submission commits are expected to take the guidelines below very seriously and attempt to conform to them to the greatest extent possible.
If you are writing a commit where you think the work is mostly done and this will likely be the message that becomes the PR description, treat it as a submission commit.
If it's not clear which of these situations applies, ask the user if they are ready for you to (a) write the final submission commit message, (b) leave it as it is, or (c) if they would like to edit/rewrite it themselves to prepare for a submission. If they want to rewrite it themselves you should still examine (but not change) the existing commit message, and suggest changes to make it aligned with the guidelines below.
Commit message guidelines
- Submission commits must follow all the unbreakable rules in the section above.
- Be concise.
- Scan for typos. If found in user-written messages, present the proposed fixes and ask for confirmation.
- Simple Formatting
- No em dashes, smart quotes, or decorative Unicode symbols.
- Plain hyphens and straight quotes only.
- Natural language characters (accented letters, CJK, etc.) are fine when the content requires them.
- Code snippets and commands in the message must be copy-paste safe.
- The purpose of a commit message is to give the reader a high-level understanding of what changed and why, but they will not remember or particularly care about the specific reproduction case that required the patch. Convey the information that is not easily apparent from inspecting the code diffs: what it's supposed to do, why, what choices were made.
- There are two audiences for the commit message: (1) the reviewer of the PR trying to understand the patch and make a merge decision; (2) somebody visiting months or years later and trying to understand what was done and why. Once the review is complete, all future visitors will be group 2, so that group matters more. Write with them in mind.
Because a PR will be required to fully pass the CI workflow to be accepted, the commit message does not need to say things that are implied by passing CI, such as any of the following:
- Tests passed locally for the submitter
- You verified that existing testsuite tests pass
- New tests added to the testsuite by the patch itself also pass
- The command used to launch ctest, any specific subset of testsuite that you ran, or the percentage of tests that passed locally
- That clang-format was run or that the formatting passes
- That the CI tests passed
- Omit any details about the submitter's local machine; it is almost always irrelevant. (Notable exceptions: if specific benchmark timing results are given, the relevant machine specs; if the point of the PR is to assure the software works on a platform not represented closely by CI, describe where it was tested.)
Describe the general class of errors fixed by the patch, do not dwell on the specific details of particular inputs that you used in the investigation (unless it is truly necessary to understand what the patch is for or how it works). For example:
- BAD: "Given a crafted input with resolution of 74067x41921, the computed allocation size was the product, 3,104,962,707, which overflows an int32." (Too specific to the one test case we investigated, and also easily discernible from the test case that is added.)
- GOOD: "Fuzzing found that very high resolution images could overflow int32 when computing allocation size. A small test reproducing this was added." (Describes the general situation that leads to the bug.)
An exception to this rule is if it's too hard to explain the nature of the bug without a specific example spelled out.
- It is not necessary to include the blow-by-blow details of the many steps of the work. Just describe the final set of changes that the squashed patch represents. Omit mentioning things that were tried and later corrected or changed in the process of developing the patch.
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
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.

