checkpoint
Save Progress with Git Checkpoints and Handoff Notes
Task switches and risky refactors can interrupt progress and leave important context behind. This skill guides a local Git checkpoint and brief handoff before work continues.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "checkpoint" from https://skillstore.io/skills/codewithmukesh-checkpoint.md and its manifest at https://skillstore.io/api/skills/codewithmukesh-checkpoint/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「checkpoint」を使用しています。 Checkpoint the validation changes before the query refactor.
期待される結果:
- Checkpoint created with a new local commit for the validation changes.
- Handoff updated with completed validation work and the pending query refactor.
- Current branch and commit recorded. No remote changes made.
「checkpoint」を使用しています。 Save progress when there are no changes to commit.
期待される結果:
- No changes to commit; no new commit created.
- Handoff updated with pending work and current branch and commit context.
セキュリティ監査
安全All 13 static findings are false positives involving Markdown formatting, routine local Git operations, or explicit secret exclusions. The workflow prohibits remote pushes and amendments while requiring selective staging. No evidence found of prompt injection, credential access, or data exfiltration.
リスク要因
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/codewithmukesh-checkpoint/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/codewithmukesh-checkpoint?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/codewithmukesh-checkpoint?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/codewithmukesh-checkpoint/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/codewithmukesh-checkpoint.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
codewithmukesh. (2026). checkpoint security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/codewithmukesh-checkpoint/audits/1BibTeX形式の引用
@techreport{codewithmukesh-codewithmukesh-checkpoint-2026,
author = {codewithmukesh},
title = {checkpoint security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/codewithmukesh-checkpoint/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "checkpoint security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "codewithmukesh"
date-released: "2026-10-31"
url: "https://skillstore.io/skills/codewithmukesh-checkpoint/audits/1"
identifiers:
- type: other
value: "skillstore:codewithmukesh-checkpoint:audit:1"
description: "Skillstore immutable audit report identifier"
バリアントを比較
インストール可能なバリアント 3 件各作者のスキルは個別のインストール項目として維持されます。推奨バリアントは Skillstore の証拠で順位付けされます。
このバリアントが首位の理由
codewithmukesh-checkpoint
2026-10-31
barnhardt-enterprises-inc-checkpoint
2026-09-09
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prepare for a Refactor
Record current implementation progress and the next refactor step before making a risky change.
Switch Maintenance Tasks
Save focused changes and pending investigation details before moving to another issue.
Resume Interrupted Work
Leave branch, commit, completed work, and next steps for a later coding session.
これらのプロンプトを試す
Create a checkpoint of my current work and summarize the handoff.
Checkpoint the current changes before refactoring [component]. Record [next step] as pending work and report the commit hash.
Checkpoint relevant changes for [current task]. Leave [remaining steps] in the handoff before switching to [next task].
Review staged and unstaged changes for [task]. Stage only [approved files], leave unrelated work untouched, and checkpoint with [next steps] in the handoff.
ベストプラクティス
- Review the diff and staged files before committing; exclude secrets, generated files, and unrelated changes.
- Use a focused commit message and record specific pending steps in the handoff.
- Run relevant checks before treating a checkpoint as a known-good state.
回避
- Staging the entire working tree without reviewing file scope.
- Treating a local checkpoint as a remote backup or proof that tests pass.
- Keeping unique historical context only in a handoff note that will be overwritten.
よくある質問
What does a checkpoint save?
Does it push changes to a remote?
What happens when there is nothing to commit?
Where is the handoff stored?
Does checkpoint run the test suite?
How does checkpoint differ from wrap-up?
開発者情報
作成者
codewithmukeshライセンス
MIT
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
b86e2308a371513cc7a7cbb5402a74131f343858
メンテナンスの新しさ
2026/10/31
利用状況
0 ダウンロード · 0 閲覧
ファイル構成
📄 SKILL.md