Push Check
Check everything before work goes to GitHub, then push it. Runs the repo's own checks, a sweep for leaked keys, personal paths, oversized files and dead links, a second Claude reading the changes cold, and a fresh-copy rehearsal of what a new user does first. Pushes only after two clean passes in a row, then drafts the short note to send people, if there is anything for them to do. Use when the user says "push", "push this", "ship it", "put it on GitHub", "release", "send it to them", "is it ready to push", or is about to share a repo other people will download.
Install
/plugin marketplace add charlie947/skills-for-everyoneThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add charlie947/skills-for-everyone --skill push-checkgit clone --depth 1 https://github.com/charlie947/skills-for-everyone.git /tmp/skills-for-everyone
mkdir -p ~/.claude/skills
cp -r /tmp/skills-for-everyone/skills/push-check ~/.claude/skills/push-checkPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# push-check
A push feels finished before it is. The checks pass, the files look fine, and the faults turn up
when someone else downloads the work: a leaked key, a link to a file that is not there, a setup
step that only works on your machine. None of it is hard to find. Nothing looked for it.
**A push is a sequence, not a command.** Every step below runs, in order, before `git push`.
The step that "obviously will pass" is the one that catches something.
Talk to the user in plain English the whole way through. They may not know git. Say what you
found and what you did about it, never which command printed it.
---
## Step 1. Say what is about to leave
```bash
git status --short
git log --oneline @{u}..HEAD 2>/dev/null || git log --oneline -10
git diff --stat @{u}..HEAD 2>/dev/null
```
Tell the user in one or two lines what this push contains: which files, and what changed for
someone who downloads it. If there is no remote yet, say so and ask where it should go before
going further. Never create a public repo without a yes. Public is the default risk.
## Step 2. Run the repo's own checks
```bash
ls tools/ scripts/ 2>/dev/null | grep -iE 'check|test|verify|validate|lint'
cat package.json 2>/dev/null | grep -A5 '"scripts"'
```
Run whatever the repo already has and **read the last line of the output**, not the first few.
A summary at the bottom that says FAIL is easy to miss when you skim from the top. If the repoDetails
- Skill name
push-check- Repository
- charlie947/skills-for-everyone
- Path
skills/push-check/SKILL.md- License
- MIT
- Repo updated
- 6 October 2026
FAQ
What does the Push Check skill do?
Check everything before work goes to GitHub, then push it. Runs the repo's own checks, a sweep for leaked keys, personal paths, oversized files and dead links, a second Claude reading the changes cold, and a fresh-copy rehearsal of what a new user does first. Pushes only after two clean passes in a row, then drafts the short note to send people, if there is anything for them to do. Use when the user says "push", "push this", "ship it", "put it on GitHub", "release", "send it to them", "is it ready to push", or is about to share a repo other people will download.
How do I install the Push Check skill?
Claude Code plugin: /plugin marketplace add charlie947/skills-for-everyone. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Push Check popular?
It lives in charlie947/skills-for-everyone, which has 10 GitHub stars and 1 forks.
Related skills
Answer First
10charlie947/skills-for-everyone
Shape every answer so the bottom line comes first. Sentence one is the answer, the number, the verdict or the one thing to do. Everything after it is support. Use when the user asks for output that is short, skimmable, action-led or "no waffle", and keep applying it for the whole conversation once invoked, not just one reply. Triggers on "answer first", "bottom line first", "no preamble", "no waffle", "keep it short", "just tell me what to do", "cut the fluff", "ADHD mode", or any request to stop burying the answer in paragraph four. It shapes Claude's replies to you, not writing you publish.
Close
10charlie947/skills-for-everyone
End a good session properly. Banks what the session taught into Claude's memory so the next session starts smarter, finishes every loose end it can, proves the changes actually landed, and hands back only what genuinely needs you. Four phases, in order: LEARN, FIX, PROVE, REPORT. Use when the user says "close", "/close", "close out", "wrap this up", "are we good to close?", "what's still open?", "anything left?", "did we miss anything", "save progress", "bank what we learned", "remember this for next time", "lock in our corrections", or otherwise signals a session is ending. Not for handing wo
Improve System
10charlie947/skills-for-everyone
Mine your own Claude Code history for what keeps going wrong, then fix it at the source. Finds corrections you had to give more than once (a rule should have stopped them), jobs you keep typing by hand (a missing skill), context you keep pasting in (a missing fact), and the kinds of work eating the most hours. Use when the user says "improve the system", "improve my setup", "what am I correcting", "what keeps going wrong", "mine my history", "what skills should I build", "why do I keep repeating myself", or once or twice a week as a routine. Also use with a topic to audit one kind of work that
Repo Wiki Detect
9boweneos/repo-wiki-agent-skills
Detect code changes since last wiki update using git diff. Identifies added, modified, deleted, and renamed files to determine which documentation pages need updates.
Carly Code Review
9carlymr/carlys-claude-skills
Comprehensive code review using 7 parallel specialized sub-agents (correctness, security, performance, simplicity, UX, codebase integration, documentation). Every finding needs a concrete failure scenario; Critical/Warning findings are then challenged by adversarial refuter agents before they reach the report. Repos can add their own reviewers via an `Extra reviewers:` list in CLAUDE.md. Use when reviewing code changes, pull requests, or local diffs. Supports local git diff (no arguments) or GitHub PR (pass PR number or URL as argument).
Zephyr Explore
9processmission/agent-skills
Use when Zephyr source, branch history, external precedent, or design constraints must be investigated before a decision can be made.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.