Menu
Commit all changes, push, wait for CI, fix if red, iterate until green
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
Report all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.
Review documentation for drift caused by the current code or configuration change. Use to identify concrete inaccuracies and, when authorized, repair only directly affected documentation.
Audit or improve general repository documentation against implemented behavior. Use for deliberate README or documentation-quality work not owned by a more specific documentation skill.
Review English technical prose without modifying it. Use for plain-English feedback on comments, docstrings, documentation, commit or pull request text, issues, reports, runbooks, logs, errors, command help, and other human-readable technical writing rather than factual or marketing review.
Audit or, when authorized, rewrite persuasive product claims against shipped-product evidence. Use for landing pages, marketing-heavy READMEs, feature or pricing pages, comparisons, and calls to action.
| name | yarstack-direct-ci-push |
| description | Commit all changes, push, wait for CI, fix if red, iterate until green |
| disable-model-invocation | true |
Follow these steps. Do NOT skip any step.
git log --oneline -5 to see recent commit message conventions in this repogit add -Agit push or git push -u origin HEAD if no upstream is set)gh run list --branch $(git branch --show-current) --limit 1 --json status,conclusion,databaseId in a loop to check CI statusIf CI is green (conclusion: "success"):
If CI is red (conclusion: "failure"):
gh run view <run-id> --log-failed