Install
$ agentstack add skill-christopherlouet-claude-base-work-commit ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Commit Message Generation
Conventional Commits Format
type(scope): short description (< 50 characters)
[optional body - details on the "what" and "why"]
[optional footer - issue references, breaking changes]
Instructions
1. Analyze the changes
# View modified files
git status --short
# View detailed diff
git diff --staged
# If nothing is staged, view non-staged changes
git diff
2. Determine the type
| Type | Usage | |------|-------------| | feat | New feature | | fix | Bug fix | | refactor | Refactoring without functional change | | test | Adding or modifying tests | | docs | Documentation only | | style | Formatting, no code change | | chore | Maintenance, dependencies | | perf | Performance improvement |
3. Identify the scope
The scope indicates the part of the code affected:
- Module name:
auth,api,ui - Component name:
button,modal - Feature:
login,checkout
4. Write the description
- Imperative present: "add" not "added" or "adds"
- Lowercase: no capital at the start
- No trailing period
- < 50 characters
5. Commit
git add [files]
git commit -m "type(scope): description"
Or with body:
git commit -m "type(scope): description
- Detail 1
- Detail 2
Refs: #123"
Rules
- ONE commit = ONE logical change
- Clear message for someone unfamiliar with the context
- Explain the WHY, not the HOW (the code shows the how)
- Reference issues if applicable
Examples
Good messages
feat(auth): add OAuth2 login support
fix(api): handle null response from external service
refactor(utils): extract date formatting to separate module
test(cart): add unit tests for price calculation
docs(readme): update installation instructions
Bad messages
❌ "fix bug" → Too vague
❌ "Update code" → Not informative
❌ "WIP" → Don't commit WIP
❌ "feat: Add new feature..." → Redundant
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: christopherlouet
- Source: christopherlouet/claude-base
- License: MIT
- Homepage: https://christopherlouet.github.io/claude-base/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.