skills.rest
miles990
miles990COMMUNITY
Explore all skills by this author →
GitHub

persist-check

Verify code and configuration changes are committed, pushed, and linked to a PR.

3|1|Updated Feb 5, 2026
Search Tags:#git#pull request#developer workflow#worktree#persistence#ci validation#delivery verification
One-click install
npx skills add https://github.com/miles990/mini-agent --skill persist-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: persist-check
Source: https://github.com/miles990/mini-agent/tree/main/.claude/skills/persist-check
Command: npx skills add https://github.com/miles990/mini-agent --skill persist-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

persist-check prevents you from claiming code or configuration work is done when the changes never actually persisted beyond the volatile runtime/main checkout.

Core Features & Use Cases

  • Verifies persistence readiness: checks that changes are committed, pushed, and have an associated PR before you report “applied/executed/completed”.
  • Guards against runtime/main volatility: ensures tracked changes aren’t accidentally made on runtime/main where they will be autocorrected away.
  • Validates through delivery signals: confirms the PR exists and that build/typecheck/tests were actually run and passed (with evidence).

Quick Start

Ask the AI to run a persist-check before saying “completed” for a change that updates code or config, and report the exact blocker if any step (worktree, commit, push, PR, validation) is missing.

Frequently Asked Questions about persist-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify my git changes are actually committed and pushed before reporting completion?▼

To verify git changes are committed and pushed, you must confirm a clean working tree, check the push delta against origin, and ensure an associated pull request exists to prove the delivery is persistent and not lost on a volatile checkout.

Why do my code changes disappear from the runtime/main checkout?▼

Code changes disappear from runtime/main checkout because it is a volatile environment where uncommitted or unpushed work is autocorrected away, making it necessary to isolate work in a worktree and persist changes via commit and push.

How do I check if a pull request has passing CI validation runs?▼

To check if a pull request has passing CI validation, you need to locate the PR via the gh CLI and ensure that real validation runs, specifically typecheck, build, and tests, have actually executed and produced passing outputs.

What is the best way to prevent losing file modifications in an automated developer workflow?▼

The best way to prevent losing file modifications in an automated developer workflow is to isolate your work in a forge-lite worktree, commit changes, push the delta to origin, and validate the pull request before claiming completion.

Does persist-check work with multi-step worktree cycles?▼

Yes, persist-check is specifically designed for multi-step cycles involving worktrees and repository automation, verifying that file changes claimed as delivered are actually persisted through commit, push, and PR rather than lost on volatile checkouts.

Related Skills

Explore More Software Engineering Skills→
saxonthunesaxonthune
1

git-sync-worktree

Rebase a worktree branch onto the latest trunk with safety checks.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

gh-check-ci-status

Check GitHub pull request CI/CD status and workflow runs via gh CLI.

Official
Intermediate
lpjhelderlpjhelder

ultraqa

Automates QA cycling to detect, diagnose and fix failing builds, lint, typecheck, and tests.

Community
Advanced
mia-cxmia-cx

gc

Group uncommitted changes into atomic conventional git commits and push them.

Official
Intermediate