skills.rest
Unsupervisedcom
UnsupervisedcomOFFICIAL
Explore all skills by this author →
WebsiteGitHub

commit.commit_and_push

Commit and push validated code changes after lint passes.

49|3|Updated Jan 11, 2026
Search Tags:#automation#git#workflow#commit#ci-cd#lint
One-click install
npx skills add https://github.com/Unsupervisedcom/deepwork --skill commit-commit-and-push
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit.commit_and_push
Source: https://github.com/Unsupervisedcom/deepwork/tree/main/.claude/skills/commit.commit_and_push
Command: npx skills add https://github.com/Unsupervisedcom/deepwork --skill commit-commit-and-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the finalization of code work by automating the verify/commit/push cycle after changes pass lint and tests.

Core Features & Use Cases

  • Strict finalization workflow: verifies changed files, stages them, and creates a meaningful commit message.
  • Automated remote push: pushes the committed changes to the configured remote repository.
  • Changelog governance: notes updates in CHANGELOG.md per workflow guidelines and enforces release discipline.
  • Use Case: Use this Skill after a successful lint pass to ensure only validated changes are committed and pushed for review or deployment.

Quick Start

Run the commit and push workflow after you have finished linting and testing. The Skill will guide you through verifying the changes, updating the changelog, committing with a compliant message, and pushing to the remote.

Frequently Asked Questions about commit.commit_and_push

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commit and push after passing lint checks?▼

Automating git commit and push after lint requires a workflow that verifies changed files, stages them, and generates a compliant commit message before pushing to the configured remote repository.

What is the best way to ensure only validated code changes are committed to version control?▼

To ensure only validated changes are committed, use a strict finalization workflow that runs after a successful lint and test pass, verifying changed files before staging and committing them to local and remote branches.

Can I update the changelog automatically when committing and pushing code?▼

You can enforce changelog governance during the commit and push cycle by applying workflow guidelines to note updates in CHANGELOG.md, ensuring release discipline before pushing changes to the remote repository.

How do I push committed changes to a remote repository with a compliant commit message?▼

Pushing committed changes requires staging verified files, creating a meaningful and compliant commit message, and executing a remote push via a provided script to sync local and remote branches.

Does the commit and push workflow work without any additional dependencies?▼

The commit and push workflow operates without additional dependencies, guiding you through verifying changes, updating the changelog, committing, and pushing to the remote after lint passes.

When should I not use an automated commit and push workflow?▼

You should not use an automated commit and push workflow before your code passes lint and tests, as the strict finalization process is designed to record only validated changes in version control.

Related Skills

Explore More Software Engineering Skills→
jtucker9jtucker9

verify

Verify completed work with automated build, test, and lint checks before committing.

Community
Advanced
BillChiricoBillChirico
5

github-pr-resolver

Resolve GitHub pull request review threads and failing CI checks with commits.

Community
Advanced
hiromailyhiromaily
126

fix-pr-review

Classify modified files and apply targeted fixes to PR review comments.

Community
Advanced
YH-05YH-05
1

push

Stage all changes, generate a commit message, and push to the remote repository.

Community
Intermediate