Skip to content
Back to skills

Fsp Checkpoint

ASecurity

Save session state — commit staged changes and write .claude/handoff.md with branch, test status, what changed, and next action.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 6, 2026
developmentgit

Security analysis

A100/100

Scanned September 6, 2026

npx -y skills add AgenticPawan/FullStack-Pilot --skill fsp-checkpoint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fsp Checkpoint?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fsp Checkpoint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agenticpawan-fsp-checkpoint/badge)](https://www.skillsdirectory.com/skills/agenticpawan-fsp-checkpoint)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fsp-checkpoint
description: Save session state — commit staged changes and write .claude/handoff.md with branch, test status, what changed, and next action.
when_to_use: /fsp-checkpoint, save state, commit and handoff, save session, write handoff, session state, checkpoint progress, end of session, handoff notes
---

Run the session-handoff skill to save current session state.

## Behavior

1. **Capture state**: Run `git status`. Note any uncommitted changes.
2. **Commit if staged**: If there are staged changes, commit them with the provided message (or prompt for one). Follow Conventional Commits (`feat(scope):`, `fix(scope):`, `chore:`, etc.).
3. **Write handoff**: Execute the session-handoff skill — write `.claude/handoff.md` with:
   - Branch name and commit state
   - What changed this session (2-4 bullets)
   - Last test run result (from `.claude/last-test-run.md` if present)
   - Next action (what to resume with in the next session)

## Arguments

- `[message]`: optional commit message. If omitted and there are staged changes, ask for one.

## Safety rules

- Never force-push.
- Never commit secrets or `.env` files.
- If the working tree is dirty (unstaged changes), list them and ask whether to stage them before committing.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…