Commit message format and task close workflow. Use when ready to commit or closing tasks.
Scanned 2/12/2026
Install via CLI
openskills install GobbyAI/gobby---
name: committing-changes
description: Commit message format and task close workflow. Use when ready to commit or closing tasks.
category: core
---
# Committing Changes - Commit and Close Workflow
This skill covers the commit message format and how to properly close tasks.
## Commit and Close Workflow
### Step 1: Stage Changes
```bash
git add <specific-files>
```
Prefer staging specific files over `git add -A`.
### Step 2: Commit with Task ID
```bash
git commit -m "[task-id] type: description"
```
Include the task ID in brackets at the start of the message.
### Step 3: Close the Task
```python
call_tool("gobby-tasks", "close_task", {
"task_id": "<task-id>",
"commit_sha": "<commit-sha>"
})
```
## Commit Message Format
```
[<task-id>] <type>: <description>
<optional body>
```
### Valid Commit Types
| Type | Use For |
|------|---------|
| `feat` | New feature |
| `fix` | Bug fix |
| `refactor` | Code restructuring |
| `test` | Adding tests |
| `docs` | Documentation |
| `chore` | Maintenance |
### Examples
```
[abc123] feat: add user authentication
[xyz789] fix: resolve password reset bug
[def456] refactor: extract auth logic to service
[ghi012] test: add unit tests for auth module
```
## Closing Without Commits
For tasks that don't require code changes (research, planning, obsolete tasks):
```python
call_tool("gobby-tasks", "close_task", {
"task_id": "<task-id>",
"reason": "obsolete" # or "already_implemented", "duplicate", "wont_fix", "out_of_repo"
})
```
## Common Mistakes
### Wrong: Close Before Commit
```python
# This will fail
call_tool("gobby-tasks", "close_task", {"task_id": "abc"})
```
### Right: Commit First, Then Close
```bash
git commit -m "[abc] feat: implement feature"
```
```python
call_tool("gobby-tasks", "close_task", {
"task_id": "abc",
"commit_sha": "a1b2c3d"
})
```
## Task Lifecycle
```
open → in_progress → review → closed
```
Tasks may enter `review` status instead of `closed` when:
- Task has `requires_user_review=true`
- Validation criteria fail
User must explicitly close reviewed tasks.
No comments yet. Be the first to comment!
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content scripts, background scripts, or i18n updates.
SEO optimization with keyword analysis, readability assessment, technical validation, content quality. Use for search rankings, blog posts, content audits, or encountering keyword density, readability scores, meta tags, schema markup errors.
Python backend development expertise for FastAPI, security patterns, database operations, Upstash integrations, and code quality. Use when: (1) Building REST APIs with FastAPI, (2) Implementing JWT/OAuth2 authentication, (3) Setting up SQLAlchemy/async databases, (4) Integrating Redis/Upstash caching, (5) Refactoring AI-generated Python code (deslopification), (6) Designing API patterns, or (7) Optimizing backend performance.
Drive the full internationalization journey for a project — detect the stack, recommend a library, set up the chosen library, wrap existing strings, and optionally connect a translation platform. Use when the user asks to add or configure i18n, internationalization, localization, multi-language support, or translations — including when they explicitly mention LinguiJS, Lingui, next-intl, "wrap strings", "find hardcoded text", "make my app translatable", or "set up translations". Triggers on g...
PTES-aligned adversarial security audit for backend, frontend, and mobile applications. Produces a CVSS-scored Hacker Report with verified PoCs and phased remediation.