Menü
Commit and push all the changes (update git ignore where needed)
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run markdown linting from tools/spec-lint/, fix issues, and rerun until clean
Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: writes a ranked checklist to plans/AUDIT.md of what to delete, simplify, or replace with stdlib/native equivalents. Use when the user says "audit this codebase", "audit for over-engineering", "what can I delete from this repo", "find bloat", or calls ponytail-audit. One-shot report, does not apply fixes.
Fix ponytail audit items from plans/AUDIT.md one at a time. For each item: implementer fix → ponytail-review → normal review → quality gate → mark done → commit. Cycle until reviewer is happy at each stage. Complements ponytail-audit.
Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "what can we delete", "is this over-engineered", "simplify review", or calls ponytail-review. Complements the correctness-focused reviewer subagent — this one only hunts complexity.
Use when executing a project folder under plans/ that contains SPEC.md, PLAN.md, and PHASE_XX.md files.
Fix the first incomplete checklist item in plans/<project>/REVIEW.md, commit the fix, then stop. Does not commit REVIEW.md — it is gitignored by design.
| name | commit-push |
| description | Commit and push all the changes (update git ignore where needed) |
This skill commits all current changes and pushes them to the remote. It ensures nothing that should be ignored leaks into the commit.
AGENTS.md at the repository root. Internalise the quality gates and project structure..gitignore at the repository root.git status to see all staged, unstaged, and untracked files.Before staging anything, review every untracked and modified file against these rules:
gen/, bin/, node_modules/, go.work.sum, compiled Go binaries.*.swp, *.swo, *~..env, credentials.json, *.pem, *.key, or anything that looks like it contains secrets. Warn the user if any are present.dist/install.yaml).If any file that should be ignored is not covered by .gitignore, update .gitignore before proceeding. Group new entries under an appropriate comment heading.
Run the repository quality gates from AGENTS.md before committing:
make test-all. If any test fails, stop and report the failure. Do not commit with failing tests.make check-fix-all. If any issue is reported, stop and report. Do not commit with lint failures.If both pass, proceed to commit.
git add -A.git diff --cached --stat to review what will be committed.git log --oneline -10).git status -sb.git push.git push -u origin HEAD.main or master — warn the user if they request it.--no-verify) unless the user explicitly requests it..gitignore is updated, include the .gitignore change in the same commit.