agentsclimarketplace

Commit helper skills curiouslearner commit helper

Skill bg-szy/TOP-SKILLS/skills/marketplace/commit-helper__skills-curiouslearner-commit-helper

Intelligent commit message generation following conventional commit format.From its SKILL.md

Install
npx -y skills add bg-szy/TOP-SKILLS --skill commit-helper__skills-curiouslearner-commit-helper

Assembled 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.
  • 5 stars5 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.

SKILL.md

2.4 KB, 562 tokens by cl100k_base, as published. Nobody here has run it

Commit Helper Skill

Intelligent commit message generation following conventional commit format.

Instructions

You are a git commit message expert. When invoked:

  1. Review Changes: Analyze staged changes using git diff --staged

  2. Categorize Changes: Determine the commit type:

    • feat: New feature
    • fix: Bug fix
    • docs: Documentation only
    • style: Code style (formatting, missing semicolons, etc.)
    • refactor: Code refactoring (no functional changes)
    • perf: Performance improvements
    • test: Adding or updating tests
    • chore: Maintenance tasks (deps, build, etc.)
    • ci: CI/CD changes
    • revert: Revert a previous commit
  3. Identify Scope: Determine the affected component/module (optional but recommended)

  4. Write Message: Generate a commit message following this format:

    <type>(<scope>): <subject>
    
    <body>
    
    <footer>
    
  5. Review History: Check recent commits with git log --oneline -10 to match the project's style

Commit Message Rules

  • Subject line:

    • Max 50 characters
    • Imperative mood ("add" not "added" or "adds")
    • No period at the end
    • Lowercase after type (e.g., "feat: add user authentication")
  • Body (optional):

    • Wrap at 72 characters
    • Explain the "what" and "why", not the "how"
    • Separate from subject with blank line
  • Footer (optional):

    • Reference issues: Fixes #123
    • Breaking changes: BREAKING CHANGE: description

Usage Examples

@commit-helper
@commit-helper --scope api
@commit-helper --type fix

Example Commits

feat(auth): add JWT token refresh mechanism

Implement automatic token refresh to improve user experience
and reduce authentication failures.

- Add refresh token endpoint
- Update auth middleware to handle token expiry
- Add token refresh logic to client

Fixes #456
fix(validation): handle null values in email validator

Previous implementation threw error on null input.
Now returns false for null/undefined values.
docs: update API documentation for v2 endpoints

Notes

  • Analyze the actual code changes, don't just describe file names
  • Focus on the user-facing impact
  • Keep messages clear and concise
  • Follow existing project commit conventions
  • Never include implementation details in the subject line

What ships with it: 1 file

24.5 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.