# AI use cases for Gitx Skill (musoyangrigor/gitx-skill)

Repo: [musoyangrigor/gitx-skill](https://github.com/musoyangrigor/gitx-skill) | Use cases: 3 | Page: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/

GitX is a portable agent skill that turns working-tree changes into logical Conventional Commits and handles branches, checks, safe push, pull requests, secret scanning and conflict resolution across skills-compatible agents.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Split messy AI changes into clean Conventional Commits: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/split-messy-changes-into-clean-commits/
- Create a branch, run checks and push safely: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/branch-check-and-open-pr/
- Set team Git conventions once in .gitx.json: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/set-team-git-conventions-in-gitx-json/

## How to split messy AI changes into clean Conventional Commits with Gitx Skill

Repo: [musoyangrigor/gitx-skill](https://github.com/musoyangrigor/gitx-skill) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Invoke one command and the agent groups your changes into logical commits with good messages.

**Who it is for:** A developer after a long agent session with dozens of unrelated file changes.

**The problem:** One giant commit makes history useless and review hard.

**The outcome:** Several logical Conventional Commits instead of one blob.

### Steps

1. Install with `npx skills add musoyangrigor/gitx-skill --skill gitx`
2. Start a new agent session
3. Run `$gitx` to inspect changes and create a smart commit
4. Use `$gitx body` when you want commit bodies

### Prompt to paste into your agent

```text
Use $gitx in <repo> to split the current changes into Conventional Commits. List the commits created and confirm no secrets were staged.
```

### Caveat

A bare $gitx immediately inspects and commits, so run it only when you are ready to commit.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/split-messy-changes-into-clean-commits/

## How to create a branch, run checks and push safely with Gitx Skill

Repo: [musoyangrigor/gitx-skill](https://github.com/musoyangrigor/gitx-skill) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README

Let the agent infer a branch name, run your project checks, and push with safe pull and push handling.

**Who it is for:** A developer who keeps forgetting to run lint and tests before pushing.

**The problem:** Pushing unchecked agent code breaks CI for everyone.

**The outcome:** A prefixed branch with checks run before it is pushed.

### Steps

1. Install GitX
2. Run `$gitx branch check` to create an inferred branch and run checks
3. Fix anything that fails
4. Push and open a pull request through GitX

### Prompt to paste into your agent

```text
In <repo>, run $gitx branch check, report the branch name and check results, and only push if all checks pass.
```

### Caveat

Checks come from your .gitx.json, so set them up first or nothing runs.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/branch-check-and-open-pr/

## How to set team Git conventions once in .gitx.json with Gitx Skill

Repo: [musoyangrigor/gitx-skill](https://github.com/musoyangrigor/gitx-skill) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Save PR base, branch prefixes, commit scopes and checks so every agent follows them.

**Who it is for:** A team lead who wants agent commits to match the team's conventions.

**The problem:** Each agent session invents its own branch names and scopes.

**The outcome:** A committed .gitx.json that every GitX run follows.

### Steps

1. Install GitX
2. Run `$gitx setup` to preview and save preferences
3. Set prBase, branchPrefix, commitScopes and checks such as npm test
4. Commit .gitx.json for the team

### Prompt to paste into your agent

```text
Run $gitx setup in <repo> with PR base <branch>, scopes <scopes> and checks <commands>. Show the resulting .gitx.json.
```

### Caveat

draftPR defaults to false in the example config.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/musoyangrigor-gitx-skill/set-team-git-conventions-in-gitx-json/