commit-push

Generate Japanese Conventional Commit messages and push staged changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ryonakae/doc-updater --skill commit-push-ryonakae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-push
Source: https://github.com/ryonakae/doc-updater/tree/main/src/.agents/skills/commit-push
Command: npx skills add https://github.com/ryonakae/doc-updater --skill commit-push-ryonakae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Eliminates manual commit message writing and the tedious, error-prone step of updating project documentation before committing and pushing code changes, ensuring commits follow Conventional Commits and docs stay in sync with staged diffs.

Core Features & Use Cases

  • Conventional Commit Generation: Produce a single Conventional Commits-style message (in Japanese) from the staged changes, selecting appropriate type and optional scope.
  • Built-in Doc Update Flow: Read and execute the doc-updater procedure from references to decide and apply documentation edits based solely on git diff --cached, then re-stage any updated docs.
  • Safe Git Operations: Validate staging state, avoid destructive operations, commit with SKIP_DOC_UPDATER=1 to prevent recursion, and push the current branch; useful for agents or developers who want automated, auditable commits that include documentation updates.

Quick Start

Ask the agent to generate a Japanese Conventional Commit message from the current staged changes, run the embedded doc-updater process if needed, stage any doc edits, commit with SKIP_DOC_UPDATER=1, and push the current branch.

Frequently Asked Questions about commit-push

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

FAQPage Schema
How do I generate Conventional Commit messages automatically from staged git changes?

Conventional Commit messages are generated automatically by reading staged git diffs to select an appropriate type and optional scope, producing a properly formatted commit message without manual writing.

How do I update documentation based on staged changes before a git commit?

Documentation updates are handled by reading the staged diff via git diff --cached, applying necessary doc edits based on those changes, and re-staging the updated documentation files before committing.

Can I automate git commit and push while keeping documentation in sync?

Git commit and push can be automated by validating the staging state, committing staged changes with synced documentation, and pushing the current branch while setting SKIP_DOC_UPDATER=1 to prevent recursive doc updates.

What is the best way to write Japanese Conventional Commit messages from git diffs?

Japanese Conventional Commit messages are written by analyzing staged changes and generating a single message in Japanese that follows the Conventional Commits format with the correct type and scope.

Does this automated commit workflow run external doc-updater CLI tools?

No external doc-updater CLI tools are invoked; the documentation update procedure runs internally by reading references and applying edits directly based on the staged git diff, avoiding external dependencies entirely.

What limitations exist when automating git staging, commit, and push operations?

This automation avoids destructive git operations and validates the staging state before proceeding, but it is limited to processing currently staged changes and does not handle unstaged modifications or branch creation.