ns-flow-cp

Creates checkpoint commits for the current git diff via the ns flow cp CLI.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill ns-flow-cp-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ns-flow-cp
Source: https://github.com/nseng-ai/ns/tree/main/skills/incubating/flow/ns-flow-cp
Command: npx skills add https://github.com/nseng-ai/ns --skill ns-flow-cp-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? During long coding sessions, developers need quick throwaway checkpoint commits to save work-in-progress without stopping to craft careful commit messages. Writing these by hand is repetitive, and sloppy checkpoints clutter the git history that later agents and reviewers scan. ## Core Features & Use Cases - Delegated Checkpoint Commits: Runs ns flow cp to stage tracked and untracked changes and create a [cp] commit with a validated 1-3 bullet message. - Safety Guardrails: The CLI refuses to checkpoint on main or master and refuses when the worktree is clean, preventing accidental or empty commits. - Use Case: Mid-refactor, before switching tasks, invoke the skill to snapshot the current diff as a [cp] checkpoint instead of typing git commit -a -m cp, keeping the log readable for later agents. ## Quick Start Ask the agent to create a checkpoint commit of the current working tree using ns flow cp.

Frequently Asked Questions about ns-flow-cp

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

FAQPage Schema
How do I create a quick checkpoint commit in git?

Run ns flow cp through this skill to stage all tracked and untracked changes and create a [cp] commit with a validated 1-3 bullet message. It replaces typing git commit -a -m cp manually.

When should I use checkpoint commits versus regular commits?

Use checkpoint commits for quick work-in-progress snapshots aimed at later agents scanning git log. Do not use them for milestone or PR-ready commits, which deserve carefully hand-authored messages.

Why does ns flow cp refuse to create a checkpoint?

The CLI refuses when the current branch is main or master, or when the worktree is clean with nothing to commit. Surface its stderr output and stop; only recover after an explicit user choice.

Can I amend or skip hooks on a checkpoint commit?

No. The skill explicitly forbids git commit --amend and git commit --no-verify for this workflow, and Co-Authored-By trailers are omitted unless the user requests a hand-authored commit.

What are the limitations of automated checkpoint commits?

Checkpoint messages are machine-oriented and minimal, so they are unsuitable for PR-ready history. The skill also depends on the ns CLI being installed and available in the environment.