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-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «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_reportЗначок Markdown
[](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/1Цитата BibTeX
@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.
Почему этот вариант первый
clouder0-checkpoint
2026-09-09
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
Актуальность поддержки
31.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md