CtrlK
BlogDocsLog inGet started
Tessl Logo

git-commit

Create well-structured git commits with conventional commit messages, proper staging, and commit best practices.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./apps/desktop/bundled-skills/git-commit/SKILL.md
SKILL.md
Quality
Evals
Security

Git Commit Helper

This skill helps create professional, well-structured git commits following best practices.

Commit Message Format

Use conventional commit format:

<type>(<scope>): <description>

[optional body]

[optional footer]

Types

  • feat: New feature
  • fix: Bug fix
  • docs: Documentation changes
  • style: Code style changes (formatting, etc.)
  • refactor: Code refactoring
  • test: Adding or modifying tests
  • chore: Maintenance tasks

Workflow

  1. Run git status to see changes
  2. Run git diff to review what changed
  3. Stage appropriate files (prefer specific files over git add .)
  4. Create commit with descriptive message
  5. Verify commit was successful

Best Practices

  • Keep commits atomic (one logical change per commit)
  • Write clear, descriptive commit messages
  • Don't commit sensitive files (.env, credentials)
  • Review changes before committing

Examples

  • "Commit my changes with a good message"
  • "Create a commit for the login feature"
  • "Stage and commit the bug fix"
Repository
accomplish-ai/coworker
Path

apps/desktop/bundled-skills/git-commit/SKILL.md

Commit

2cf74d0

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill