القائمة
Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Sync this Claude Code config against new release notes — find config features added since the pinned baseline that this config should adopt. Use when Claude Code has been updated, when the user asks what's new / what changed / whether to adopt new settings or hooks, after a version bump, or when checking config currency against the latest release. Reports adoptable settings/hooks/env-vars/permissions as a risk-tiered proposal, then bumps the baseline. Do NOT use for auditing existing config quality, debugging hooks, or organizing rules — that is `maintaining-claude-code`.
Monitor and watch GitHub Actions CI/CD pipeline runs in real time. Use when the user has pushed code and wants to watch the build, check CI status, see if tests passed, monitor a pipeline, or wait for a workflow run to complete. Also use after any `jj git push` or `git push` command. Reports pass/fail with failed job logs. Do NOT use for writing or editing CI workflow YAML files, optimizing CI config, or debugging CI configuration — only for monitoring active runs.
Reorganize and clean up messy commit history on a feature branch into logical, reviewable commits. Use when cleaning up commits, preparing a branch for review, separating formatting from logic changes, fixing broken intermediate states, or squashing WIP commits.
Audit and improve Claude Code hooks, rules, and settings.json. Use when adding/debugging a hook, organizing rules, auditing settings.json (permissions, env vars, stale flags), or deciding between hook vs skill vs rule vs CLAUDE.md. For SKILL.md authoring use the skill-creator plugin; for CLAUDE.md audits use the claude-md-improver plugin.
Search past Claude Code sessions to recall prior solutions, commands, fixes, and decisions. Use when the user references earlier work ("how did I fix", "last time we", "pick up where we left off", "a few months ago", "what was that … I set up", "didn't I once").
Query, create, and manage Linear issues from the command line. Use when checking assigned work, viewing issue details, creating new issues, or updating issue status.
| name | executing-test-plans |
| description | Execute a structured test plan and emit a concise results document (JSON + Markdown). Use when running test plans, executing QA workflows, verifying acceptance criteria systematically, or producing test results documentation. |
| argument-hint | [plan-file] [env-profile] [out-dir] |
| allowed-tools | ["Bash(curl:*)","Bash(docker:*)","Bash(aws sqs:*)","Bash(mysql:*)","Bash(jq:*)","Bash(grep:*)","Bash(watch:*)"] |
Execute test plans end-to-end with strict state control and concise reporting.
suggested_adjustmentsBLOCKED with reasonstatus = PASS | FAIL | BLOCKEDdocker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}" | head -20Document clearly:
Write <out-dir>/test-results.json with this schema:
{
"metadata": {
"sut": "",
"env": {},
"plan_sections": 0,
"timestamp": ""
},
"sections": [
{
"id": "",
"title": "",
"precheck_ok": true,
"pre_state": { "assessed": [], "actions": [], "ready": true },
"inputs": [],
"outputs": [],
"expected": [],
"comparison": { "match": true, "diffs": [] },
"status": "PASS",
"suggested_adjustments": [],
"notes": []
}
],
"overall": {
"pass_rate": "0/0",
"failing_or_blocked_sections": [],
"verdict": "PASS"
}
}
Also write a human-readable Markdown summary alongside the JSON.