Stage, commit, and push verified code changes with conventional commits.
npx skills add https://github.com/mitchellfyi/dex --skill dxcommit
Please help me install this Agent Skill. Skill: dxcommit Source: https://github.com/mitchellfyi/dex/tree/main/skills/dxcommit Command: npx skills add https://github.com/mitchellfyi/dex --skill dxcommit
Manually staging changes, writing consistent conventional commit messages, and configuring push targets for new feature branches leads to inconsistent git history, accidental inclusion of sensitive files, and broken push workflows that waste developer time on tedious git hygiene.
Use the dxcommit skill to stage, commit, and push your verified code changes following the repository's commit guidelines.
High-intent search queries and answers about installing and using this skill.
Automating git conventional commits and pushes is handled by staging only specific files per logical change group, applying the repository's required commit format and co-author trailers, and configuring upstream remotes for new feature branches to ensure safe push operations.
Preventing accidental bulk staging of unrelated git changes requires atomic commit staging, which selectively stages only specific files per logical change group rather than automatically staging all modified files in the working directory.
Blocking forbidden files and unapproved force pushes in a git workflow is achieved through commit discipline enforcement that prevents sensitive file inclusion during staging and blocks unapproved force pushes during push operations to protect branch history.
This commit automation skill works directly with the Dex ticket-to-PR system, handling atomic conventional commits, required co-author trailer injection, and upstream remote configuration specifically for new Dex lifecycle feature branches.
Automated conventional commit formatting for feature branches is needed after code changes pass quality verification gates, eliminating manual git overhead and ensuring consistent repository history with proper commit discipline and co-author attribution.
Manual git commit and push workflows lead to inconsistent version control history because manually staging changes, writing conventional commit messages, and configuring push targets introduces human error, accidental sensitive file inclusion, and broken push configurations.
NagyViktStage, commit, and push verified changes to non-default Git branches with conventional messages.
markmhendricksonPush the current Git branch to origin with submodule scoping and pre-push checks.
avvaleCommit changes, push to a feature branch, and create a GitHub Pull Request.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
