Automate Git commits and pushes with conventional messages and PR comments.
npx skills add https://github.com/Vulnetix/vdb-api --skill commit-feature
Please help me install this Agent Skill. Skill: commit-feature Source: https://github.com/Vulnetix/vdb-api/tree/main/.claude/skills/commit-feature Command: npx skills add https://github.com/Vulnetix/vdb-api --skill commit-feature
This Skill streamlines the process of committing code changes by automating staging, conventional commit message generation, pushing to origin, and creating detailed Pull Request comments with session context.
feat api to automatically commit your changes, push them, and add a detailed summary to the associated Pull Request, informing reviewers about the implementation and any outstanding tasks.Run the commit-feature skill with the type 'feat' and scope 'api'.
High-intent search queries and answers about installing and using this skill.
Automating git commit and push workflows involves staging all changes, parsing commit types and scopes to generate conventional commit messages, and pushing the commits directly to origin. This removes manual staging and message formatting from your development cycle.
Generating detailed pull request comments requires collecting session context including implementation details, tracked tasks, known issues, and technical debt. This context is automatically parsed and appended to the PR to inform reviewers about the implementation state.
The automated commit process does not include co-authorship tags in the git history. It explicitly creates commits without co-authorship, ensuring a clean commit log that solely attributes changes to the primary developer.
You can specify commit types and scopes like feat and api for automated git commits. The system parses the provided type and scope arguments to structure the conventional commit message accurately before staging and pushing changes.
The best way to document implementation details and known issues for a pull request is to automatically collect session context and generate comprehensive PR comments. This extracts tasks, known issues, and technical debt directly from the session.
Pull request comments missing session tasks and technical debt after a git push indicate a failure in session context collection. The automation must successfully parse implementation details and known issues before appending them to the PR comment.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
mvillmowSyncs Git worktrees by fetching remote and rebasing or merging main into feature branches.
julianobarbosaAutomate Git commits with pre-commit security scans and Conventional Commits enforcement.
RoentekStage the git working tree and generate a Conventional Commits message.