commit-task

Commit Volon task changes with configured git commit modes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hollis-labs/volon --skill commit-task
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-task
Source: https://github.com/hollis-labs/volon/tree/main/plugins/git/skills/commit-task
Command: npx skills add https://github.com/hollis-labs/volon --skill commit-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates creating consistent Git commits for completed tasks in a Volon workspace, removing manual staging and commit-message construction and ensuring commits follow the project's configured commit mode.

Core Features & Use Cases

  • Config-aware commits: Reads git.commit_mode and git.auto_commit from volon.yaml to determine iteration or isolated commit behavior and whether to skip committing.
  • Task identification: Locates an explicit .volon/tasks/<task-id>.md or the most recently completed task when no ID is provided.
  • Safe staging and commit: Checks git status, warns on unrelated changes, stages files, and commits using iteration or isolated message formats, then prints the commit hash and changed files.
  • Use case: After finishing QA on a task, run this Skill to automatically stage relevant worktree changes and produce a standardized commit message for review or pushing.

Quick Start

Commit the most recently completed task using the repository's configured commit mode.

Frequently Asked Questions about commit-task

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

FAQPage Schema
How do I automate git commits for completed Volon tasks?▼

You can automate git commits for completed tasks by running this Skill, which reads your volon.yaml configuration, stages worktree changes, and generates a standardized commit using your project's designated commit mode.

What is the difference between iteration and isolated commit modes in Volon?▼

Iteration and isolated commit modes are git.commit_mode settings in volon.yaml that determine how this Skill formats commit messages when finalizing a completed task in a Volon workspace.

Can I skip automatic git commits if auto_commit is disabled in volon.yaml?▼

If git.auto_commit is disabled in volon.yaml, this Skill honors that configuration and skips the commit process, ensuring changes are not committed automatically when finalizing Volon tasks.

How do I commit a specific Volon task by its ID?▼

To commit a specific Volon task by its ID, this Skill locates the explicit .volon/tasks/<task-id>.md file, stages the associated repository changes, and commits them using your configured mode.

What happens to unrelated git changes when committing a Volon task?▼

When committing a Volon task, this Skill checks git status and warns you about unrelated changes before staging, ensuring only relevant worktree files are included in the commit.

Does this Skill output the commit hash and changed files list?▼

Yes, this Skill outputs the commit hash and a list of changed files after creating the git commit, providing metadata for review or pushing within your version-control workflow.