Skill

cp

Commit and push in one step. Use when user says "/cp", "commit and push", "커밋하고 푸시", "커밋 푸시", or wants to stage, commit, and push changes in a single action. Optionally accepts a commit message as argument.

From cp
Install
1
Run in your terminal
$
npx claudepluginhub october-academy/agent-plugins --plugin cp
Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Commit & Push Skill

Streamlined git workflow: stage, commit, and push in one command.

Usage

Basic

/cp                        # Auto-generate commit message
/cp "fix: resolve bug"     # Use provided message

Korean Triggers

  • "커밋하고 푸시"
  • "커밋 푸시"
  • "변경사항 올려줘"

Workflow

1. Analyze Changes

git status                 # See all changes
git diff --staged          # Staged changes
git diff                   # Unstaged changes
git log -3 --oneline       # Recent commits for context

2. Generate Commit Message

If no message provided, analyze changes and generate following Conventional Commits:

PrefixUse Case
feat:New feature
fix:Bug fix
docs:Documentation
refactor:Code restructuring
style:Formatting (no logic change)
test:Adding tests
chore:Maintenance tasks

3. Stage Files

Prefer specific files over git add -A:

git add src/component.tsx src/utils.ts

Never stage:

  • .env files
  • Credentials or secrets
  • Large binary files (unless intentional)

4. Commit

Use HEREDOC for proper formatting:

git commit -m "$(cat <<'EOF'
type: concise description

Optional body with more details.

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

5. Push

git push origin <current-branch>

If upstream not set:

git push -u origin <current-branch>

Safety Checks

Before committing:

  1. No secrets: Scan for API keys, passwords, tokens
  2. Correct branch: Verify not pushing to protected branch accidentally
  3. Clean diff: Review what's being committed

Error Handling

ErrorSolution
"Nothing to commit"No changes detected, inform user
"Push rejected"Run git pull first, then retry
"Pre-commit hook failed"Fix issues, stage again, create NEW commit
Similar Skills
cache-components

Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.

138.5k
Stats
Parent Repo Stars0
Parent Repo Forks1
Last CommitFeb 3, 2026