Gcm
skill dump
npx -y skills add usrrname/agent-skills --skill gcmAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate conventional commit message from staged or unstaged changes
SKILL.md
1.2 KB, as published. Nobody here has run it
Generate a conventional commit message for the current changes.
Process
- Run
git log --oneline -10and match the existing commit style. - Run
git diff --cachedto read staged changes. If empty, rungit difffor unstaged changes. - Generate the commit message following the rules below.
Format
<type>(<scope>): <description>
<body>
Types
fix, feat, docs, style, refactor, test, chore, spelling, rename
Scope
Infer from changed file paths. If changes span multiple scopes, use the most significant one or omit the scope.
Body
Include a body when the change is non-trivial. Explain why, not what. Separate from title with a blank line. Wrap at 72 characters.
Breaking changes
If the change is breaking, add ! after the scope and a BREAKING CHANGE: footer:
feat(sdk)!: rename updateSnapshot to updateProject
BREAKING CHANGE: updateSnapshot removed, use updateProject(projectId, { snapshotId }) instead.
Additional context
$@