Chalk Labs
Need help deploying commit-message?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/sur1ive-commit-message
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: writing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/commit-message
What's inside
- Skill name
commit-message- Description
- Write a clear git commit message (Conventional Commits). Use when the user asks to commit, or to write/fix a commit message.
- License
- MIT
- Instructions
- 21 lines in SKILL.md · view on GitHub
Files (1)
- SKILL.md
SKILL.md (first lines)
# Writing commit messages
1. Look at what actually changed first: `git status` and `git diff --staged`
(or `git diff` if nothing is staged). Never describe changes you have not seen.
2. Subject line: `<type>(<optional scope>): <summary>`
- type: feat | fix | docs | refactor | test | perf | build | ci | chore
- imperative mood ("add", not "added"), no trailing period, <= 72 chars
3. Blank line, then a body only if the *why* is not obvious from the subject.
Wrap at 72 columns. Explain motivation and trade-offs, not the diff line by line.
4. Breaking changes: add `!` after the type and a `BREAKING CHANGE:` footer.
5. One logical change per commit. If the diff mixes two, suggest splitting it.
Examples:
fix(ship): retry once on network timeout
feat(api)!: drop the v1 /payments endpoint
BREAKING CHANGE: clients must call /v2/payments.From Sur1ive/harness-from-scratch, MIT.
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Oct 12, 2026 (18 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/Sur1ive/harness-from-scratch
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from Sur1ive
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get commit-message running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
commit-message skill. Agent Mart. https://agentmart.dev/skills/sur1ive-commit-message (last updated 2026-10-24)