ToolJet Multi-Repo Commit
ToolJet/ToolJet
Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.
Fold fixups into a branch without losing a message, a marker or somebody else's branch — the amend!
Install History Rewriting
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic history-rewriting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/history-rewriting .claude/skills/history-rewriting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "history-rewriting" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewriting into .claude/skills/history-rewriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history-rewriting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewritingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic history-rewriting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/history-rewriting .agents/skills/history-rewriting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "history-rewriting" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewriting into .agents/skills/history-rewriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history-rewriting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic history-rewriting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/history-rewriting .cursor/skills/history-rewriting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "history-rewriting" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewriting into .cursor/skills/history-rewriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history-rewriting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/stylelint-stylistic/stylelint-stylistic.git --path .agents/skills/history-rewriting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic history-rewriting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/history-rewriting .gemini/skills/history-rewriting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "history-rewriting" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewriting into .gemini/skills/history-rewriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history-rewriting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install stylelint-stylistic/stylelint-stylistic history-rewritingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/history-rewriting .github/skills/history-rewriting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "history-rewriting" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewriting into .github/skills/history-rewriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history-rewriting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install stylelint-stylistic/stylelint-stylistic history-rewriting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/stylelint-stylistic/stylelint-stylistic.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/history-rewriting .opencode/skills/history-rewriting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "history-rewriting" agent skill from https://github.com/stylelint-stylistic/stylelint-stylistic/tree/main/.agents/skills/history-rewriting into .opencode/skills/history-rewriting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "history-rewriting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
history-rewriting- GitHub stars
- 106
- Token cost
- ~826 tokens
- SKILL.md length
- 436 words
- Files
- 1
- Skills in repo
- 6
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Fold fixups into a branch without losing a message, a marker or somebody else's branch — the amend!
- Tasks that involve Commit messages
- SKILL.md covers The amend! file, What a rebase does behind your… and The pre-commit hook's copy has…
- Calls git, vitest and make
- Tasks that involve Git workflow
What it does
History Rewriting is an agent skill from stylelint-stylistic/stylelint-stylistic. Fold fixups into a branch without losing a message, a marker or somebody else's branch — the amend! file's shape, what rebase --continue and a zero-exit editor really do, rebase.updateRefs, and the pre-commit hook's blind spot. Use before git commit --fixup, git rebase --autosquash, a rebase that rewrites a commit message, or a commit the hook refuses.
Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Commit messages and Git workflow. It works with Git. The repository describes itself as: A collection of stylistic rules for Stylelintin in a form of a plugin.
When your agent uses it
- Tasks that involve Commit messages
- Tasks that involve Git workflow
Example prompts
- “s branch — the amend! file”
- “/history-rewriting”
What it can do on your machine
Read from SKILL.md and the folder at commit 52bbb57. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitvitestmake
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
History Rewriting loads about 826 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 436 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 436 words (~826 tokens).
“Every one of these ends with git saying it succeeded. Read git log --oneline after each step rather than the command's last line.”
- name
- history-rewriting
Files
Just SKILL.md in .agents/skills/history-rewriting of stylelint-stylistic/stylelint-stylistic.
Open the folder on GitHubat commit 52bbb57
Compare with similar skills
History Rewriting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| History Rewriting this skillstylelint-stylistic/stylelint-stylistic | 106 | — | ~826 | Automated safety check: Pass | Custom licence | |
| ToolJet Multi-Repo CommitToolJet/ToolJet | 41k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Git Workflow and Versioningaddyosmani/agent-skills | 105k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| React Router Pull Request Creatorremix-run/react-router | 57k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Saleor Commit Workflowsaleor/saleor | 23k | — | ~575 | Automated safety check: Pass | BSD-3-Clause | |
| Emoji Commit ConventionsbaptisteArno/typebot.io | 11k | — | ~424 | Automated safety check: Pass | Custom licence |
Similar skills
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
Saleor Commit Workflow
saleor/saleor
Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
More from stylelint-stylistic/stylelint-stylistic
Base Comparison
stylelint-stylistic/stylelint-stylistic
Measure a branch against the commit it stands on — extract the base instead of flipping the working tree, pick the base by hash, and prove a new test case red on it.
Engine Probes
stylelint-stylistic/stylelint-stylistic
Ask a real engine what a stylesheet means instead of reasoning about tokens — the Less compiler, lightningcss, dart-sass, and a custom syntax's own parser.
Outward Prose
stylelint-stylistic/stylelint-stylistic
Write a commit body, a changelog entry, a PR body, an issue comment or a code comment so that no sentence in it is a claim nobody ran.
Stacks And Issues
stylelint-stylistic/stylelint-stylistic
The GitHub mechanics of this repository — building and re-rooting a gh stack, why CI runs on the bottom PR alone, which hash is stable after a merge, and how an umbrella issue closes.
Sweeps And Oracles
stylelint-stylistic/stylelint-stylistic
Build a corpus that can see the change, and read what the oracles and sweeps report without over-reading it.
Related
Works with
Categories
Questions about History Rewriting
What does History Rewriting do?
Fold fixups into a branch without losing a message, a marker or somebody else's branch — the amend! History Rewriting is an agent skill from stylelint-stylistic/stylelint-stylistic. Fold fixups into a branch without losing a message, a marker or somebody else's branch — the amend!
When should I use History Rewriting?
History Rewriting fits situations like: tasks that involve Commit messages; tasks that involve Git workflow.
How do I install History Rewriting in Claude Code?
Run `npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a claude-code`. Or copy the skill folder (.agents/skills/history-rewriting in stylelint-stylistic/stylelint-stylistic) into .claude/skills/history-rewriting in your project. Claude Code loads it when a task matches its description.
How do I install History Rewriting in Codex?
Run `npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a codex`. Or copy the skill folder (.agents/skills/history-rewriting in stylelint-stylistic/stylelint-stylistic) into .agents/skills/history-rewriting in your project. Codex loads it when a task matches its description.
Can I use History Rewriting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add stylelint-stylistic/stylelint-stylistic --skill history-rewriting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/history-rewriting, .gemini/skills/history-rewriting, .github/skills/history-rewriting and .opencode/skills/history-rewriting in your project.
What does History Rewriting need to run?
Going by SKILL.md and its folder, History Rewriting needs the command-line tools its instructions call (git, vitest and make).
Does History Rewriting access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is History Rewriting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does History Rewriting use?
History Rewriting has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does History Rewriting use?
About 826 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to History Rewriting?
Skills that share tags, products or a category with History Rewriting: ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 105k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Saleor Commit Workflow (saleor/saleor, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains History Rewriting?
stylelint-stylistic (a GitHub organization) maintains it in stylelint-stylistic/stylelint-stylistic, which has 106 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 11, 2026.
Source: stylelint-stylistic/stylelint-stylistic on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.