Menu
Commit all staged/unstaged changes and push to remote. Use proactively for committing and pushing changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Create blog posts — from a topic (writes content) or with provided content (scaffolding). Use proactively when creating new blog posts or articles.
Pre-publication audit for blog posts — comprehensive final review of SEO, AEO, accessibility, images, content quality, i18n parity, and project conventions before publishing. Use proactively before publishing any blog post.
Pre-publication audit for blog series — validates series definition, post ordering, cross-post consistency, navigation, and runs individual post audits for all posts in the series. Use proactively before publishing any blog series.
Audit the blog tag taxonomy — frequency analysis, orphan detection, hierarchy validation, and proposals for new subtopic tags. Read-only — proposes, never modifies tags or posts. Use proactively before each release cycle or after a content drop of 5+ posts.
Optional DeepWorkPlan addon that connects an AI-first repo to the developer's Dailybot team — installing (with consent) the Dailybot agent skill (DailybotHQ/agent-skill) and/or the Dailybot CLI (DailybotHQ/cli), wiring the plan lifecycle into best-effort agent updates - kickoff when a plan starts, significant task completions, a blocked report when an unattended run halts, and a milestone on plan completion - with payloads derived from the plan's state layer, and optionally committing the Dailybot skill's deterministic hook enforcement (dailybot hook lifecycle hooks, CLI >= 1.12.0) so the agent harness itself reminds agents about unreported work. Opt-in, never required, never blocks the work, reconciles existing setups instead of clobbering them, and defers all auth to the Dailybot skill's own consent flow. Use when the developer or team already uses Dailybot and wants DWP progress visible to humans.
Optional DeepWorkPlan addon that safely upgrades a repo's dependencies — reasoning about the repo's ACTUAL package manager (npm/pnpm/yarn + ncu, pip/poetry/uv, cargo, go mod, bundler, composer, and more) rather than assuming npm — with a batched, validated, revertible workflow that detects the manager and manifests/lockfiles, classifies upgrades (patch/minor/major), upgrades in safe batches, runs the repo's real validation gate after each batch, reverts a failing batch, and summarizes. Opt-in, never required, reconciles with the repo's existing tooling. Use when the developer wants to bring dependencies up to date without breaking the build.
| name | git-commit-push |
| description | Commit all staged/unstaged changes and push to remote. Use proactively for committing and pushing changes. |
| disable-model-invocation | false |
| allowed-tools | Read, Glob, Grep, Bash |
| model | haiku |
| tier | 1 |
| intent | execute |
| max-files | unlimited |
Commit all current changes with a well-crafted conventional commit message and push to the remote repository.
Tier: 1 - Light/Cheap
Reasoning: This is a mechanical, low-risk task that follows established patterns (conventional commits). The AI analyzes changes and generates an appropriate commit message.
$MESSAGE: Custom commit message (default: auto-generated from changes)$SCOPE: Commit scope override (default: inferred from files)Before running this skill, ensure:
Review current repository state:
git status
If working tree is clean, report "Nothing to commit" and stop.
Analyze what changed:
git diff --stat
git diff HEAD
Identify:
Review commit message style:
git log --oneline -5
Follow the repository's existing commit message conventions.
Add all changes:
git add -A
Generate a conventional commit message based on changes:
git commit -m "$(cat <<'EOF'
<type>(<scope>): <description>
<body if needed>
EOF
)"
Commit Types:
feat: New featurefix: Bug fixdocs: Documentation onlyrefactor: Code change that neither fixes a bug nor adds a featuretest: Adding or updating testschore: Maintenance tasksPush to the current branch:
git push
If upstream not set:
git push -u origin HEAD
Verify the push:
git status
git log --oneline -1
## ✅ Committed and Pushed
### Commit
`<commit-hash>` <commit-message>
### Branch
<branch-name> → origin/<branch-name>
### Changes
- <N> files changed
- <N> insertions(+), <N> deletions(-)
### Files
- <file1>
- <file2>
...
## ℹ️ Nothing to Commit
Working tree is clean. No changes to commit.
## ❌ Commit Failed
### Error
<error message>
### Suggestion
<how to resolve>
Stop immediately if:
Ask user if:
Context: User updated a blog component
Execution:
git add -A
git commit -m "fix(blog): handle empty search query gracefully"
git push
Output:
## ✅ Committed and Pushed
### Commit
`a1b2c3d` fix(blog): handle empty search query gracefully
### Branch
fix/blog-search → origin/fix/blog-search
### Changes
- 2 files changed
- 15 insertions(+), 3 deletions(-)
Context: User added dark mode support to a component
Execution:
git add -A
git commit -m "feat(theme): add dark mode to footer component
- Add dark mode Tailwind classes
- Update color scheme
- Test with theme toggle"
git push
Output:
## ✅ Committed and Pushed
### Commit
`d4e5f6g` feat(theme): add dark mode to footer component
### Branch
feature/dark-mode-footer → origin/feature/dark-mode-footer
### Changes
- 3 files changed
- 45 insertions(+), 12 deletions(-)
Context: User says "commit and push" but no changes exist
Output:
## ℹ️ Nothing to Commit
Working tree is clean. No changes to commit.
quick-fix - Often used before this skillpr-review-lite - Review before committing| Version | Date | Changes |
|---|---|---|
| 1.0.0 | 2024-01 | Initial version |