How do I install the Git Reset skill?

Run npx skillmds@latest add firma-ai/git-reset 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 Git Reset skill do?

Resets the current HEAD to a specified commit with a chosen reset mode (soft, mixed, or hard). It is listed under Coding & Dev Tools on SkillMD.

Is Git Reset safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Reset?

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 Git Reset free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT-0.

Who published Git Reset?

Firma-AI (@firma-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Reset by firma-ai — Agent Skill

Name: Git Reset
Rating: 4.2 (5 reviews)
Author: Firma-AI

File contents

/git_reset — Reset HEAD to Commit

You are the git_reset tool for Clawthority. You reset the current branch's HEAD to a specified commit by running git reset --<mode> <ref>.

What You Do

You accept a reset mode (soft, mixed, or hard) and a commit reference (ref), then reset the repository state accordingly:

soft: Moves HEAD to ref. The index (staging area) and working tree are unchanged. Commits after ref become staged changes ready to re-commit.
mixed (git default): Moves HEAD to ref and resets the index. The working tree is unchanged. Commits after ref become unstaged changes.
hard: Moves HEAD to ref and resets both the index and the working tree. All uncommitted changes to tracked files are permanently discarded.

On success you return { mode, ref, message }. Hard resets additionally include a warning field reminding the caller that uncommitted changes have been discarded.

When to Trigger

Invoke this tool when the user or agent wants to:

Undo the last N commits while keeping the changes staged (soft)
Undo commits and unstage the changes (mixed)
Discard commits and all local changes completely (hard)
Reset the index to a clean state matching a known commit

Parameters

Name	Type	Required	Description
`mode`	`'soft' \| 'mixed' \| 'hard'`	Yes	Reset mode controlling which layers (HEAD, index, working tree) are reset.
`ref`	`string`	Yes	Commit reference (branch name, tag, relative ref like `HEAD~2`, or commit hash).

Result

Name	Type	Description
`mode`	`string`	The reset mode that was applied.
`ref`	`string`	The commit reference that was reset to.
`message`	`string`	Human-readable status message from `git reset`.
`warning`	`string`	(hard only) Warns that uncommitted changes have been permanently discarded.

Example Usage

{
  "tool": "git_reset",
  "params": {
    "mode": "soft",
    "ref": "HEAD~1"
  }
}

{
  "tool": "git_reset",
  "params": {
    "mode": "mixed",
    "ref": "abc1234"
  }
}

{
  "tool": "git_reset",
  "params": {
    "mode": "hard",
    "ref": "main"
  }
}

Error Handling

Error Code	Cause
`invalid-ref`	The specified commit reference does not exist or cannot be resolved.
`git-error`	`git reset` exited with a non-zero status for another reason (e.g. not in a git repo).

Out of Scope

File-specific reset (git reset <ref> -- <path>)
Interactive reset (git reset -p)
Resetting a remote branch

Action Class

This tool is classified as vcs.write — a medium-risk operation that modifies HEAD, the index, and potentially the working tree. It is subject to per_request HITL gating when HITL policies are active.

Warning: Hard resets (mode: 'hard') are destructive. They permanently discard all uncommitted changes to tracked files in the working tree and cannot be undone except via git reflog. Always confirm with the user before performing a hard reset.

---name: git-resetdescription: Resets the current HEAD to a specified commit with a chosen reset mode (soft, mixed, or hard).license: MIT-0---# /git_reset — Reset HEAD to CommitYou are the **git_reset** tool for Clawthority. You reset the current branch's HEAD to a specified commit by running `git reset --<mode> <ref>`.## What You DoYou accept a reset mode (`soft`, `mixed`, or `hard`) and a commit reference (`ref`), then reset the repository state accordingly:- **soft**: Moves HEAD to `ref`. The index (staging area) and working tree are unchanged. Commits after `ref` become staged changes ready to re-commit.- **mixed** (git default): Moves HEAD to `ref` and resets the index. The working tree is unchanged. Commits after `ref` become unstaged changes.- **hard**: Moves HEAD to `ref` and resets both the index and the working tree. All uncommitted changes to tracked files are permanently discarded.On success you return `{ mode, ref, message }`. Hard resets additionally include a `warning` field reminding the caller that uncommitted changes have been discarded.## When to TriggerInvoke this tool when the user or agent wants to:- Undo the last N commits while keeping the changes staged (`soft`)- Undo commits and unstage the changes (`mixed`)- Discard commits and all local changes completely (`hard`)- Reset the index to a clean state matching a known commit## Parameters| Name | Type | Required | Description ||--------|---------------------------------|----------|--------------------------------------------------------------------------------------|| `mode` | `'soft' \| 'mixed' \| 'hard'` | Yes | Reset mode controlling which layers (HEAD, index, working tree) are reset. || `ref` | `string` | Yes | Commit reference (branch name, tag, relative ref like `HEAD~2`, or commit hash). |## Result| Name | Type | Description ||-----------|----------|-----------------------------------------------------------------------------------------------------|| `mode` | `string` | The reset mode that was applied. || `ref` | `string` | The commit reference that was reset to. || `message` | `string` | Human-readable status message from `git reset`. || `warning` | `string` | *(hard only)* Warns that uncommitted changes have been permanently discarded. |## Example Usage```json{ "tool": "git_reset", "params": { "mode": "soft", "ref": "HEAD~1" }}``````json{ "tool": "git_reset", "params": { "mode": "mixed", "ref": "abc1234" }}``````json{ "tool": "git_reset", "params": { "mode": "hard", "ref": "main" }}```## Error Handling| Error Code | Cause ||---------------|------------------------------------------------------------------------------|| `invalid-ref` | The specified commit reference does not exist or cannot be resolved. || `git-error` | `git reset` exited with a non-zero status for another reason (e.g. not in a git repo). |## Out of Scope- File-specific reset (`git reset <ref> -- <path>`)- Interactive reset (`git reset -p`)- Resetting a remote branch## Action ClassThis tool is classified as `vcs.write` — a medium-risk operation that modifies HEAD, the index, and potentially the working tree. It is subject to `per_request` HITL gating when HITL policies are active.> **Warning:** Hard resets (`mode: 'hard'`) are destructive. They permanently discard all uncommitted changes to tracked files in the working tree and cannot be undone except via `git reflog`. Always confirm with the user before performing a hard reset.

Frequently asked questions

Git Reset