القائمة
Check GitHub Actions workflow status, diagnose failures, fetch logs, and fix common build issues. Use when builds fail, deploys break, or you need to investigate CI/CD problems.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Critique book prose in the author's voice using patterns learned from his own git edit history (not a hand-written rubric). Use when asked to "voice-check", "punch up", "make this sound like me / like Vonnegut / like Cunk", or to review whether a passage is too pompous / cute / self-aware. Catches what the regex scanner (voice-check.py, ~1.4% of real edits) misses.
Review and improve QMD chapter writing quality by replacing boring/consultant text with Wishonia's deadpan alien voice, consolidating redundancy, and reducing word count. Use when asked to fix voice, make content funnier, remove jargon, or enforce the book's writing style.
Spawns parallel agents to review all paperback QMD files. Reads variable-resolved previews, flags judgment-required issues with REVIEW comments.
Automated book maintenance. Runs health checks, prioritizes work, and systematically fixes issues. Use when you want Codex to autonomously improve the book.
Critically analyze a calculated parameter for academic rigor. Checks methodology, identifies weaknesses, suggests improvements for economist audiences.
Systematic book curation pipeline. Evaluates every chapter on 8 dimensions, identifies overlaps, and produces a scored report with actionable recommendations.
| name | check-github-actions |
| description | Check GitHub Actions workflow status, diagnose failures, fetch logs, and fix common build issues. Use when builds fail, deploys break, or you need to investigate CI/CD problems. |
Check the most recent completed workflow run and fix any failures.
gh run list --limit 5 to find recent runsgh run view RUN_ID to see which jobs failed and their error annotationsGitHub Actions Status
--------------------
Run #[ID] ([time] ago): [X]/13 jobs passed
Failed Jobs:
- [Job Name]: [Brief error description]
Fix: [What you changed]
Status: [Fixed/Needs commit/Other action needed]
Focus on fixing, not explaining. Keep output concise.