git-checkpoint
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.
62
72%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./agentscope-examples/agents/agentscope-codingagent/src/main/resources/workspace-templates/skills/git-checkpoint/SKILL.mdGit 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-verifyRecord 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.
- Repository
- agentscope-ai/agentscope-java
- Commit
1a81e59
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.