commit-and-push

To automate a git commit and push workflow without a release, this skill inspects your repository state, normalizes project docs, generates a Conventional Commit message, and pushes changes directly to the current branch without creating tags or releases.

To convert completed specs into project documentation before committing, the workflow applies archive-specs for spec conversion and normalizes non-standard docs, ensuring categorized documentation is included in the final push.

Yes, you can run code validations before pushing. The workflow coordinates optional code-affecting checks and validates required dependencies prior to generating a commit message and pushing to the current branch.

Yes, this commit and push workflow preserves staging intent. It inspects git status, diffs, and staged changes to determine the exact change set, ensuring your partially staged files are committed exactly as intended.

The best way to classify local repository changes for a Conventional Commit is to inspect the git state and diffs to determine the exact change set, which then dictates the concise conventional commit message emitted before pushing.

You should use a deterministic workflow for pushing local changes to prevent accidental releases. It strictly submits local repository changes with a commit and push action to the current branch, deliberately avoiding any versioning, tags, or release triggers.