A streamlined utility for committing and pushing code changes to a remote repository.
Install
mkdir -p .claude/skills/cnp && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17256" && unzip -o skill.zip -d .claude/skills/cnp && rm skill.zipInstalls to .claude/skills/cnp
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
\ubcc0\uacbd\uc0ac\ud56d \ucee4\ubc0b \ud6c4 \ub9ac\ubaa8\ud2b8 \ud478\uc2dcKey capabilities
- →Check git status for changes
- →Analyze git diff for modifications
- →Review recent commit styles
- →Draft commit messages in English Conventional Commits style
- →Stage changed files individually, excluding sensitive ones
- →Commit and push changes to remote
How it works
The skill automates the process of checking git status, analyzing diffs, drafting commit messages in English Conventional Commits style, staging files, and pushing to the remote. It includes checks for sensitive files and branch protection.
Inputs & outputs
When to use cnp
- →Committing and pushing changes in one command
- →Formatting commit messages automatically
- →Safe handling of git remote sync
About this skill
cnp
Use this skill when the user asks to run the cnp workflow.
Command Template
현재 브랜치의 변경사항을 커밋하고 리모트에 푸시하는 커맨드.
$ARGUMENTS로 커밋 메시지 힌트를 받을 수 있다. 예: /cmp 키패드 버그 수정
절차
- 상태 확인:
git status로 변경사항을 확인한다. 변경사항이 없으면 사용자에게 알리고 중단한다. - diff 확인:
git diff와git diff --staged로 변경 내용을 파악한다. - 커밋 로그 확인:
git log --oneline -5로 최근 커밋 스타일을 확인한다. - 커밋 메시지 작성: 변경 내용을 분석하여 영어 Conventional Commits 스타일로 커밋 메시지를 작성한다.
$ARGUMENTS가 있으면 의미만 힌트로 활용하고 최종 메시지는 영어로 쓴다. - 스테이징: 변경된 파일을 개별적으로
git add한다..env, 자격 증명 파일 등 민감한 파일은 제외한다. - 커밋 및 푸시: 확인 없이 바로 커밋하고 푸시한다.
- 푸시: 리모트 트래킹 브랜치가 있으면
git push, 없으면git push -u origin <브랜치이름>으로 푸시한다.
주의사항
develop이나main브랜치에서 직접 커밋하려는 경우 사용자에게 경고하고 확인을 받는다.- 커밋 메시지는 반드시 영어로 작성한다. 한국어를 쓰지 않는다.
.env,credentials.json등 민감한 파일이 변경사항에 포함되어 있으면 스테이징에서 제외하고 사용자에게 알린다.console.log가 포함된 변경사항이 있으면 사용자에게 알린다.- 위 경고 상황을 제외하면 확인 없이 바로 진행한다.
Codex Invocation
Use this as a Codex project skill. Invoke cnp with the issue id and flags as described above; treat the user text after the skill name as ``.
When not to use it
- →When committing directly on `develop` or `main` without confirmation
- →When commit messages are not in English
- →When sensitive files like `.env` or `credentials.json` are to be staged
Limitations
- →Commit messages must be written in English.
- →Sensitive files like `.env` and `credentials.json` are excluded from staging.
- →Changes containing `console.log` are flagged.
How it compares
This skill simplify the commit and push process by automating status checks, diff analysis, and commit message formatting, while also enforcing safeguards against sensitive file exposure and direct commits to protected branches.
Compared to similar skills
cnp side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| cnp (this skill) | 0 | 2mo | Review | Beginner |
| github-release-management | 4 | 5mo | Review | Advanced |
| agent-release-swarm | 1 | 5mo | Review | Advanced |
| magerun-release | 1 | 5mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
github-release-management
ruvnet
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management
agent-release-swarm
ruvnet
Agent skill for release-swarm - invoke with $agent-release-swarm
magerun-release
netz98
Technical release process for n98-magerun2
release
ziggy42
Use this skill when the user wants to cut a new release.
release-branch
mono
Create a release branch for SkiaSharp. Use when user says "release X", "start release X", "create release branch for X", "I want to release", or "release now". This is the FIRST step of releasing - creates branch and pushes to trigger CI. Can auto-detect next preview version from main branch.
release-minor
knuckleswtf
Automates the process of tagging a new minor release for Scribe by analyzing commit messages, updating the changelog, and creating a GitHub release.