skills.rest
GobbyAI
GobbyAIOFFICIAL
Explore all skills by this author →
WebsiteGitHub

committing-changes

Enforce task-referencing commit messages and close tasks via gobby-tasks.

19|3|Updated Dec 15, 2025
Search Tags:#git#workflow#commit#task-management#version-control#task-id
One-click install
npx skills add https://github.com/GobbyAI/gobby --skill committing-changes-gobbyai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: committing-changes
Source: https://github.com/GobbyAI/gobby/tree/main/src/gobby/install/shared/skills/committing-changes
Command: npx skills add https://github.com/GobbyAI/gobby --skill committing-changes-gobbyai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes commit messages and enables closing tasks from a single workflow.

Core Features & Use Cases

  • Commit message format enforcement: Ensure each commit references a task ID in brackets and a concise type description.
  • Integrated task closure: Close tasks via the gobby-tasks tool after successful commits.
  • Lifecycle guidance: Guides users through open → in_progress → review → closed task progression with clear steps.

Quick Start

Stage changes with git add <specific-files>. Commit using the task-aware message: git commit -m "[<task-id>] <type>: <description>". Close the task once committed: call_tool("gobby-tasks", "close_task", { "task_id": "<task-id>", "commit_sha": "<commit-sha>" }).

Frequently Asked Questions about committing-changes

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

FAQPage Schema
How do I enforce a git commit message format that includes a task ID?▼

To enforce a git commit message format, this skill requires each commit to reference a task ID in brackets followed by a concise type description, ensuring consistent version control history across your software development workflow.

What is the best way to close a task automatically after committing code changes?▼

The best way to close a task after committing code changes is to use the gobby-tasks tool. You call the close_task action with the specific task ID and commit SHA to progress the task lifecycle to closed.

How does task lifecycle progression work when committing changes with version control?▼

Task lifecycle progression during version control commits moves tasks through open, in_progress, review, and closed stages. The workflow guides you to close the task only after the related code changes are successfully committed.

How do I write a task-aware commit message in git?▼

You write a task-aware commit message in git using the format: git commit -m "[<task-id>] <type>: <description>". This structure ensures every code change is directly linked to its corresponding task identifier.

Can I use this commit workflow for software development contexts where tasks must reference specific IDs?▼

Yes, you can use this workflow for software development contexts requiring task ID references. It standardizes commit messages and integrates task closure to ensure tasks are closed only after code changes are committed.

Related Skills

Explore More Software Engineering Skills→
guidodinelloguidodinello
1

conventional-commits

Generate granular conventional commits from staged Git changes.

Community
Advanced
sumrae412sumrae412
2

shipping-workflow

Automate conventional commits, pull requests, and 10-step code review before merging.

Community
Advanced
GobbyAIGobbyAI
19

tasks

Automate task creation, updates, and tracking via the gobby-tasks MCP server.

Official
Intermediate
dorriodorrio

ln-742-precommit-setup

Configure Husky, lint-staged, commitlint, and Python pre-commit hooks.

Community
Intermediate