agentsclimarketplace

Commit and push

Skill winetree94/devtools/skills/commit-and-push

CLI for web research and agent skill workflows.

Install
npx -y skills add winetree94/devtools --skill commit-and-push

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 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

Commit

SKILL.md

1.8 KB, as published. Nobody here has run it

Analyze current changes and create well-organized commits.

Instructions

  1. Review recent commit history

    • Check the last 10 git commits to understand the project's commit message style and conventions
    • Follow the same format, tone, and structure for consistency

  2. Analyze current changes

    • Run git status and git diff to understand all staged and unstaged changes
    • Group related changes by their purpose (e.g., feature work, bug fixes, documentation, refactoring)

  3. Split commits by purpose

    • Do NOT create a single commit for unrelated changes
    • Create separate commits for each logical unit of work
    • Each commit should be atomic and represent a single purpose

  4. Commit message format

    • Use a conventional commit prefix:
      • feat: - new features
      • fix: - bug fixes
      • docs: - documentation changes
      • chore: - maintenance tasks, dependency updates
      • refactor: - code refactoring without behavior change
      • style: - formatting, whitespace changes
      • test: - adding or updating tests
      • i18n: - internationalization changes
    • Write concise, descriptive messages focusing on "why" rather than "what"
    • Keep the subject line under 72 characters

  5. Push to remote

    • After all commits are created, push to the remote repository

  6. Use English

    • All commit messages MUST be written in English
    • Use clear, professional technical English
    • Follow standard English grammar and sentence structure
    • Use imperative mood (e.g., "Add feature" not "Added feature")
    • Examples:
      • feat: add user profile page
      • fix: resolve timeout error during login
      • docs: add installation guide to README
      • refactor: extract authentication logic into separate module

Keep looking

Skills are one crate of 328,083. 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.