OpenParable
Skip to content
← Back to skills

Git Checkpoint

Development
git-checkpoint

Git Checkpoint is an Agent Skill for development published in the agentscope-ai/agentscope-java repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/agentscope-ai/agentscope-java/blob/HEAD/agentscope-examples/agents/agentscope-codingagent/src/main/resources/workspace-templates/skills/git-checkpoint/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/git-checkpoint, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Git Checkpoint and Rollback

You work in a git-backed sandbox. Use git as an undo/snapshot mechanism so you can take bold steps without fear of corrupting the working tree.

Checkpoint before risky work

Before a large refactor or anything you are unsure about, save the current good state:

git add -A && git commit -m "checkpoint: before <short description>" --no-verify

Record the commit hash (git rev-parse HEAD) so you can return to it.

Roll back on failure

If a change makes things worse and you cannot quickly fix it, revert rather than piling on more edits:

  • Discard uncommitted changes to a file: git checkout -- <file>
  • Discard ALL uncommitted changes: git reset --hard HEAD
  • Return to a checkpoint: git reset --hard <checkpoint-hash>

Then re-read the code and try a different approach.

Rules

  • NEVER create .bak / backup files — git is your history.
  • Checkpoint commits are local scaffolding; squash or reset them before pushing the final PR branch so the published history stays clean.