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.

2026-06-252

ponytail-fix

really-knows-ai/gideas

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.

2026-06-252

ponytail-review

really-knows-ai/gideas

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.

2026-06-242

execute-phased-plan

really-knows-ai/gideas

Use when executing a project folder under plans/ that contains SPEC.md, PLAN.md, and PHASE_XX.md files.

2026-06-242

fix-review-item

really-knows-ai/gideas

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.

2026-06-232

name	commit-push
description	Commit and push all the changes (update git ignore where needed)

Overview

This skill commits all current changes and pushes them to the remote. It ensures nothing that should be ignored leaks into the commit.

Entry Point

Read AGENTS.md at the repository root. Internalise the quality gates and project structure.
Read .gitignore at the repository root.
Run git status to see all staged, unstaged, and untracked files.

Pre-Commit Checks

Gitignore Audit

Before staging anything, review every untracked and modified file against these rules:

Generated files must be ignored: gen/, bin/, node_modules/, go.work.sum, compiled Go binaries.
Editor artifacts must be ignored: *.swp, *.swo, *~.
Secrets and credentials must never be committed: .env, credentials.json, *.pem, *.key, or anything that looks like it contains secrets. Warn the user if any are present.
Build output should not be committed unless it is an intentionally-distributed artifact (e.g. 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.

Quality Gates

Run the repository quality gates from AGENTS.md before committing:

Tests — Run make test-all. If any test fails, stop and report the failure. Do not commit with failing tests.
Lint — Run make check-fix-all. If any issue is reported, stop and report. Do not commit with lint failures.

If both pass, proceed to commit.

Commit

Stage all changes: git add -A.
Run git diff --cached --stat to review what will be committed.
Draft a commit message:
- Summarise the nature of the changes (new feature, enhancement, bug fix, refactor, docs, etc.).
- Focus on the "why" rather than the "what".
- Keep it to 1-2 concise sentences.
- Follow the style of recent commits in the repository (git log --oneline -10).
Present the commit message and the list of files to the user for confirmation before committing.
Once confirmed, create the commit.

Push

Check if the current branch tracks a remote branch: git status -sb.
If the branch tracks a remote, push: git push.
If the branch does not track a remote, push with upstream tracking: git push -u origin HEAD.
Report the result — confirm success or surface any push errors.

Rules

Never force-push unless the user explicitly requests it.
Never force-push to main or master — warn the user if they request it.
Never skip pre-commit hooks (--no-verify) unless the user explicitly requests it.
Never commit files that contain secrets. Warn the user and exclude them.
Always show the user the commit message and file list before committing. Wait for confirmation.
If quality gates fail, stop and report. Do not commit broken code.
If .gitignore is updated, include the .gitignore change in the same commit.