菜单
Review recent GitHub Actions workflow runs, separate expected noise from actionable failures, and write a machine-readable workflow health report for deterministic post-agent issue handling.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | keppo:check-workflows |
| description | Review recent GitHub Actions workflow runs, separate expected noise from actionable failures, and write a machine-readable workflow health report for deterministic post-agent issue handling. |
Review recent GitHub Actions workflow runs from the last N hours and write a JSON report to the path in $WORKFLOW_HEALTH_REPORT_PATH.
$ARGUMENTS: optional lookback window in hours. Default to 24 when it is missing or invalid.gh run list and gh run view with the provided read-only GitHub token. Do not create issues, comments, labels, or any other GitHub mutations directly.action_required or neutral conclusionsmain branchesmain branch CI failures with the same root causegh run list --limit 100 --json workflowName,status,conclusion,event,headBranch,createdAt,databaseId,url,name
gh run view <run_id> --log-failed
Always write exactly one JSON object to $WORKFLOW_HEALTH_REPORT_PATH.
If no actionable issue exists:
{
"status": "healthy",
"summary": "Markdown summary of what was checked and why no issue is needed."
}
If an actionable issue exists:
{
"status": "action_required",
"summary": "Markdown summary of the actionable problems.",
"issue": {
"dedupeKey": "stable-kebab-case-key-for-this-problem-cluster",
"title": "Concise issue title naming the workflow problem",
"body": "Markdown issue body for a newly created issue.",
"updateComment": "Markdown comment to post when an open issue with the same dedupe key already exists."
}
}
dedupeKey must stay stable for the same underlying problem cluster.summary should state:
body and updateComment should include:
Review recent code changes and broad codebase areas for critical and high severity security vulnerabilities. Use when Codex needs to clear `./out-security-review`, select 25 non-doc, non-test files split across past-day commits, past-week commits, and broad codebase coverage, group them into 6-8 review buckets, spawn one security-review sub-agent per review bucket, persist each candidate finding to `./out-security-review/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for responsible disclosure.
Record a short Playwright-based product demo video for significant UI or user-visible functionality changes. Use when Codex needs to show a workflow in motion for a PR, either by recording an existing targeted E2E spec or by creating a disposable one-off Playwright spec that captures the changed behavior in under a minute, then uploading the final video to Vercel Blob and preparing a PR comment body that says "Demo at commit {hash}" with a 1-2 sentence summary and durable hosted link.
Review the last 7 days of recent commits for large architecture improvements that dramatically improve maintainability. Use when the agent needs to clear `./out-code-architect`, select 25 non-doc, non-test files from recent commits across different parts of the repo, spawn one architecture-review sub-agent per starting file, persist each candidate finding to `./out-code-architect/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for issue filing.
Review the last 7 days of recent commits for critical and high severity bugs that break user experience. Use when the agent needs to clear `./out-bug-finder`, select 25 non-doc, non-test files from recent commits across different parts of the repo, spawn one bug-review sub-agent per starting file, persist each candidate finding to `./out-bug-finder/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for issue filing.
Print the full host-side `scripts/pr.sh` command needed to create or switch to a feature branch, commit current changes, push, and open or update a PR outside the Docker sandbox using explicit flag-style inputs.
Commit all working-tree and untracked changes in git, then push to the current branch using an automatically generated Conventional Commit message.