fixup
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: fixup
description: Create a fixup commit and autosquash rebase You are assisting with fixing up an existing commit…
category: data
runtime: no special runtime
---
# fixup output preview
## PART A: Task fit
- Use case: Create a fixup commit and autosquash rebase You are assisting with fixing up an existing commit using interactive rebase. Follow these steps: If there are uncommitted changes: git commit --fixup=<commit-hash> Run non-interactive rebase with autosquash: git rebase --autosquash origin/main makes outbound network calls. Works with Claude Code, Cursor, Cline ….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “1. Initial Assessment / 2. Create Fixup Commit / 3. Autosquash Rebase” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create a fixup commit and autosquash rebase You are assisting with fixing up an existing commit using interactive rebase. Follow these steps: If there are uncommitted changes: git commit --fixup=<commit-hash> Run non-interactive rebase with autosquash: git rebase --autosquash origin/main makes outbound network calls. Works with Claude Code, Cursor, Cline …”.
- **02** When the source has headings, the agent prioritizes “1. Initial Assessment / 2. Create Fixup Commit / 3. Autosquash Rebase” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.The source mentions slash commands such as `/publish`; use them first when your agent supports command triggers.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “1. Initial Assessment / 2. Create Fixup Commit / 3. Autosquash Rebase”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: fixup
description: Create a fixup commit and autosquash rebase You are assisting with fixing up an existing commit…
category: data
source: majiayu000/claude-skill-registry
---
# fixup
## When to use
- Create a fixup commit and autosquash rebase You are assisting with fixing up an existing commit using interactive reba…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “1. Initial Assessment / 2. Create Fixup Commit / 3. Autosquash Rebase” and keep inference separate from source facts.
- read files, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "fixup" {
input -> user goal + target files + boundaries + acceptance criteria
context -> 1. Initial Assessment / 2. Create Fixup Commit / 3. Autosquash Rebase
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Fixup
You are assisting with fixing up an existing commit using interactive rebase. Follow these steps:
1. Initial Assessment
- Run
git statusto see if there are uncommitted changes - Run
git fetch originto 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 stageCreate a fixup commit:
git commit --fixup=<commit-hash>
3. Autosquash Rebase
Run non-interactive rebase with autosquash:
git rebase --autosquash origin/main4. Commit Message Review
After rebase completes, verify the commit message matches the changes:
Display the rebased commit:
git show HEAD --statCompare the commit message body with the actual changes
If the message is inaccurate or incomplete:
- Draft a corrected commit message following the
commit-messagerule - Explain what needs to be updated and why
- Update with
git commit --amend
- Draft a corrected commit message following the
5. Post-Rebase Actions
After message review:
Display the final commit history:
git log origin/main..HEAD --onelineInform the user to run
/publishto push changes and update the PR
Key Principles
- Use
--fixup=<hash>to create fixup commits targeting specific commits --autosquashautomatically merges fixup commits during rebase- Review commit messages after rebase - compare with actual changes
- Update messages with
git commit --amendwhen they don't accurately reflect the changes - Commit messages follow the
commit-messagerule
Decide Fit First
Design Intent
How To Use It
Boundaries And Review