How do I install the Syntrixbase Syntrix Commit Changes skill?

Run npx get-skill add tomevault-io/syntrixbase-syntrix-commit-changes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Syntrixbase Syntrix Commit Changes skill do?

Commit Changes It is listed under Coding & Dev Tools on SkillMD.

Is Syntrixbase Syntrix Commit Changes safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Syntrixbase Syntrix Commit Changes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Syntrixbase Syntrix Commit Changes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Syntrixbase Syntrix Commit Changes?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Syntrixbase Syntrix Commit Changes by tomevault-io

Name: Syntrixbase Syntrix Commit Changes
Author: tomevault-io

File contents

Commit Changes

Instructions

Analyze Changes: Run git diff --staged, git diff, and git status
Stage All: Use git add -A if needed
Understand Context: What changed, why, type, scope, patterns
Check Branch: If on main/master, create descriptive branch first
Generate Message: Subject ≤72 chars, imperative, conventional type
Execute: git commit -m "<message>"

Commit Message Format

<type>(<scope>): <subject>

<body>

Types

Type	Use Case
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only
`style`	Formatting, no code change
`refactor`	Code restructuring
`test`	Adding/fixing tests
`chore`	Build, config, dependencies

Rules

Imperative mood ("Add feature" not "Added feature")
No trailing period
Subject ≤72 characters
Body explains what/why, not how
No co-author credits or "Generated with..." tags

Quality Standards

Meaningful to someone reading git log months later
Avoid generic: "fix bug", "update code"
Group related changes conceptually
Flag if changes too diverse for single message

Edge Cases

Situation	Action
No changes	Inform user nothing to commit
Incomplete changes	Flag observation to user
On main/master	Create feature branch first
Too diverse	Note to user, suggest splitting

Examples

Example 1: Feature Commit

feat(auth): add JWT token refresh mechanism

- Implement automatic token refresh before expiration
- Add refresh token storage in secure cookie
- Include retry logic for failed refresh attempts

Example 2: Bug Fix Commit

fix(api): prevent null pointer on empty response

Handle case where API returns empty body instead of
throwing unhandled exception in response parser.

Example 3: Refactor Commit

refactor(streamer): extract common mock to shared helper

- Move mockGRPCStreamClient to mock_query.go
- Consolidate 4 duplicate mock implementations
- Reduce test file coupling

Example 4: Multi-scope Commit

test(streamer): consolidate redundant tests

- Remove TestRemoteStream_Success (duplicate of Recv_EventDelivery)
- Merge Close_Idempotent into TestRemoteStream_Close
- Delete tests with no real assertions

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: syntrixbase-syntrix-commit-changesdescription: Commit Changes---# Commit Changes## Instructions1. **Analyze Changes**: Run `git diff --staged`, `git diff`, and `git status`2. **Stage All**: Use `git add -A` if needed3. **Understand Context**: What changed, why, type, scope, patterns4. **Check Branch**: If on main/master, create descriptive branch first5. **Generate Message**: Subject ≤72 chars, imperative, conventional type6. **Execute**: `git commit -m "<message>"`## Commit Message Format```<type>(<scope>): <subject><body>```### Types| Type | Use Case ||------|----------|| `feat` | New feature || `fix` | Bug fix || `docs` | Documentation only || `style` | Formatting, no code change || `refactor` | Code restructuring || `test` | Adding/fixing tests || `chore` | Build, config, dependencies |### Rules- Imperative mood ("Add feature" not "Added feature")- No trailing period- Subject ≤72 characters- Body explains **what/why**, not how- No co-author credits or "Generated with..." tags## Quality Standards- Meaningful to someone reading git log months later- Avoid generic: "fix bug", "update code"- Group related changes conceptually- Flag if changes too diverse for single message## Edge Cases| Situation | Action ||-----------|--------|| No changes | Inform user nothing to commit || Incomplete changes | Flag observation to user || On main/master | Create feature branch first || Too diverse | Note to user, suggest splitting |## Examples### Example 1: Feature Commit```feat(auth): add JWT token refresh mechanism- Implement automatic token refresh before expiration- Add refresh token storage in secure cookie- Include retry logic for failed refresh attempts```### Example 2: Bug Fix Commit```fix(api): prevent null pointer on empty responseHandle case where API returns empty body instead ofthrowing unhandled exception in response parser.```### Example 3: Refactor Commit```refactor(streamer): extract common mock to shared helper- Move mockGRPCStreamClient to mock_query.go- Consolidate 4 duplicate mock implementations- Reduce test file coupling```### Example 4: Multi-scope Commit```test(streamer): consolidate redundant tests- Remove TestRemoteStream_Success (duplicate of Recv_EventDelivery)- Merge Close_Idempotent into TestRemoteStream_Close- Delete tests with no real assertions```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/syntrixbase) — claim your Tome and manage your conversions.

Frequently asked questions

Syntrixbase Syntrix Commit Changes