cp

Verify, stage, commit, and push code changes on the current branch.

52|12|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dgk-dev/dgk-gpt --skill cp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cp
Source: https://github.com/dgk-dev/dgk-gpt/tree/main/skills/cp
Command: npx skills add https://github.com/dgk-dev/dgk-gpt --skill cp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a safe local gate before code changes are committed and pushed, ensuring that only intentional work is captured in version history and that unrelated or unverified files are not accidentally committed.

Core Features & Use Cases

  • Local verification before commit: runs checks to confirm readiness and safety of changes.
  • Explicit staging: prompts you to stage only the files you intend to include.
  • Commit on the current branch: commits on the active branch, with guidance for conventional messaging.
  • Push with guardrails: pushes to the repository while preserving safeguards, reducing accidental pushes to main/master.
  • Use Case: finishing a feature after implementation by finalizing and pushing a clean, review-friendly commit.

Quick Start

Run the cp skill to verify, stage, commit, and push changes on the current branch.

Frequently Asked Questions about cp

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

FAQPage Schema
How do I prevent accidental commits of unverified files in git?

To prevent accidental commits of unverified files, you need a local verification gate that explicitly stages only intended changes. This ensures unrelated files are not captured in version history before a commit is created.

What is the safest way to stage and push code changes on the current branch?

The safest way to stage and push changes is to use a wrapper that enforces explicit staging and push guardrails. This reduces the risk of accidental pushes to main or master by verifying readiness on the active branch first.

How do I automate conventional commit messaging and pushing?

You can automate conventional commit messaging and pushing by using a local wrapper that finalizes your feature with a clean, review-friendly commit. It guides the commit format and safely pushes with safeguards.

Does this local verification wrapper work with any repository workflow?

Yes, this local verification wrapper works regardless of repository workflow. It commits on the active branch using deterministic local checks, ensuring only intended work is pushed without relying on specific repository configurations.

Why do I need explicit staging before a local commit?

You need explicit staging before a local commit to guarantee that only intentional work is captured in version history. It prompts you to select specific files, preventing unverified or unrelated changes from being included accidentally.