fixup

Data Community

Repo stars 330
License MIT
Author repo claude-skill-registry

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Create a fixup commit and autosquash rebase You are assisting with fixing up an existing commit using interactive rebase. Follow…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “1. Initial Assessment”, “2. Create Fixup Commit”, “3. Autosquash Rebase”, “4. Commit Message Review”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name fixup directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “1. Initial Assessment / 2. Create Fixup Commit / 3. Autosquash Rebase” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Fixup

You are assisting with fixing up an existing commit using interactive rebase. Follow these steps:

1. Initial Assessment

Run git status to see if there are uncommitted changes
Run git fetch origin to get latest remote updates
Display existing commits with git log origin/main..HEAD --oneline

2. Create Fixup Commit

If there are uncommitted changes:

Show the commit history
Ask user which commit hash to fixup (or identify it based on context)
Stage changes with git add . or ask which files to stage
Create a fixup commit:
```
git commit --fixup=<commit-hash>
```

3. Autosquash Rebase

Run non-interactive rebase with autosquash:

git rebase --autosquash origin/main

4. Commit Message Review

After rebase completes, verify the commit message matches the changes:

Display the rebased commit:
```
git show HEAD --stat
```
Compare the commit message body with the actual changes
If the message is inaccurate or incomplete:
- Draft a corrected commit message following the commit-message rule
- Explain what needs to be updated and why
- Update with git commit --amend

5. Post-Rebase Actions

After message review:

Display the final commit history:
```
git log origin/main..HEAD --oneline
```
Inform the user to run /publish to push changes and update the PR

Key Principles

Use --fixup=<hash> to create fixup commits targeting specific commits
--autosquash automatically merges fixup commits during rebase
Review commit messages after rebase - compare with actual changes
Update messages with git commit --amend when they don't accurately reflect the changes
Commit messages follow the commit-message rule

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Data
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 94 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @majiayu000 · MIT
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: External requests
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview fixup.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Fixup

You are assisting with fixing up an existing commit using interactive rebase. Follow these steps:

## 1. Initial Assessment

- Run `git status` to see if there are uncommitted changes
- Run `git fetch origin` to get latest remote updates
- Display existing commits with `git log origin/main..HEAD --oneline`

## 2. Create Fixup Commit

If there are uncommitted changes:

1. Show the commit history
2. Ask user which commit hash to fixup (or identify it based on context)
3. Stage changes with `git add .` or ask which files to stage
4. Create a fixup commit:

   ```bash
   git commit --fixup=<commit-hash>
   ```

## 3. Autosquash Rebase

Run non-interactive rebase with autosquash:

```bash
git rebase --autosquash origin/main
```

## 4. Commit Message Review

After rebase completes, verify the commit message matches the changes:

1. Display the rebased commit:

   ```bash
   git show HEAD --stat
   ```

2. Compare the commit message body with the actual changes

3. If the message is inaccurate or incomplete:
   - Draft a corrected commit message following the `commit-message` rule
   - Explain what needs to be updated and why
   - Update with `git commit --amend`

## 5. Post-Rebase Actions

After message review:

1. Display the final commit history:

   ```bash
   git log origin/main..HEAD --oneline
   ```

2. Inform the user to run `/publish` to push changes and update the PR

## Key Principles

- Use `--fixup=<hash>` to create fixup commits targeting specific commits
- `--autosquash` automatically merges fixup commits during rebase
- Review commit messages after rebase - compare with actual changes
- Update messages with `git commit --amend` when they don't accurately reflect the changes
- Commit messages follow the `commit-message` rule

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> 1. Initial Assessment → 2. Create Fixup Commit → 3. Autosquash Rebase → 4. Commit Message Review → 5. Post-Rebase Actions → Key Principles
terms    -> You are assisting with fixing up an existing commit using interactive rebase. · 1. Show the commit history 2.
files/cmd -> git status · git fetch origin · git log origin/main..HEAD --oneline · git add . · commit-message · git commit --amend · /publish · --fixup=<hash>
body sha256 -> 7bff6bfb1af5