Skip to content
Back to skills

Checkpoint 3

DSecurity

Create a safe checkpoint git commit on the current branch (avoid competition data, runs, artifacts, secrets).

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
securitysqlrailsgit

Security analysis

D50/100
  • criticalReads or references SSH private keys
  • criticalReads or references SSH private keys

Pro shows the line behind each finding and how to fix it

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill checkpoint-3 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Checkpoint 3?

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

Security grade badge for Checkpoint 3
[![Security: D — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-checkpoint-3/badge)](https://www.skillsdirectory.com/skills/david-li0406-checkpoint-3)

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: checkpoint
description: Create a safe checkpoint git commit on the current branch (avoid competition data, runs, artifacts, secrets).
---

When invoked (or when the user says `checkpoint`), do this in order.

## 1) Preflight (must do; show output)
- `git status`
- `git diff --stat`

## 2) Sanity guardrails (must do)
- Never run: `git push`, `git commit --amend`, `git rebase`, `git reset --hard`, `git clean -fdx`, or modify git remotes.
- Never stage/commit secrets/credentials: `.env*`, `*.pem`, `*.key`, `id_rsa*`, `id_ed25519*`, tokens.
- Never stage/commit competition data or run artifacts:
  - `competitions/**/{public,private,raw,downloads}/**`
  - `runs/**`
  - sqlite/db files

## 3) Stage (default: include safe tracked files)
Stage only source/docs/config files and small markdown:
- root `*.md`, `*.yml`
- `docs/**`
- `local_context_enrichments/**`
- `.codex/**`

If anything looks suspicious (bulk files, data-like payloads), stop and report before staging.

Before committing, show:
- `git diff --cached --stat`

## 4) Commit (auto message)
- Create a structured message that includes the agent id:
  - `agentNN: checkpoint(<area>): <short summary>`
  - Derive `agentNN` from `agent_logs/current.md` (field `id:`). If missing, stop and ask the human.
  - Choose `<area>` from: `workflow`, `docs`, `orchestrator`, `competitions`, `prompts`, `ci`, `misc`.
- Run `git commit -m "<message>"`.

## 5) Postflight (must do; show output)
- `git status`
- Report the commit hash.

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…