メニュー
Pull latest skills from claude-harness repo and sync to ~/.claude/skills/ and ~/.codex/skills/. Run this in any project to get the latest enterprise skills. Use when the user says 'update skills', 'sync skills', 'pull latest harness', or invokes /harness-update.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | harness-update |
| description | Pull latest skills from claude-harness repo and sync to ~/.claude/skills/ and ~/.codex/skills/. Run this in any project to get the latest enterprise skills. Use when the user says 'update skills', 'sync skills', 'pull latest harness', or invokes /harness-update. |
Pull latest skills from the claude-harness repo and deploy full skill directories to Claude Code and Codex.
SKILL.md; copy each full skill directory so scripts, evals,
templates, references, and agents metadata stay usable.~/.claude/skills or
~/.codex/skills.skills-index package is available.cd ~/claude-harness && git pull origin main
for skill_dir in ~/claude-harness/skills/*; do
[ -d "$skill_dir" ] || continue
name=$(basename "$skill_dir")
case "$name" in
*-workspace) continue ;;
esac
mkdir -p ~/.claude/skills/"$name" ~/.codex/skills/"$name"
rsync -a --delete --exclude='node_modules/' --exclude='__pycache__/' "$skill_dir"/ ~/.claude/skills/"$name"/
rsync -a --delete --exclude='node_modules/' --exclude='__pycache__/' "$skill_dir"/ ~/.codex/skills/"$name"/
done
if [ -d ~/claude-harness/skills-index ]; then
cd ~/claude-harness/skills-index
npm rebuild better-sqlite3 sqlite-vec >/dev/null 2>&1 || true
npm run index -- --repo-root "${CLAUDE_PROJECT_DIR:-$PWD}" || true
fi
python3 ~/.codex/skills/.system/skill-creator/scripts/quick_validate.py ~/.claude/skills/diagnose
python3 ~/.codex/skills/.system/skill-creator/scripts/quick_validate.py ~/.codex/skills/diagnostic-cohort
python3 ~/.codex/skills/.system/skill-creator/scripts/quick_validate.py ~/.codex/skills/zoom-out
echo "Claude skills: $(ls ~/.claude/skills/*/SKILL.md 2>/dev/null | wc -l)"
echo "Codex skills: $(ls ~/.codex/skills/*/SKILL.md 2>/dev/null | wc -l)"
echo "Harness version: $(cd ~/claude-harness && git describe --tags --always)"
Print the count and version to the user. Done.
Project-grounded blast-radius tracing for code changes, PRs, diffs, files, symbols, or bugfixes, especially in Helpdesk-style repos. Use before editing, committing, merging, or reviewing when downstream callers, tests, routes, SQL, configs, schema, auth/tenant boundaries, external integrations, sibling bugs, or review-derived trap replays could be affected.
Standard rigorous multi-agent pipeline for bugs and build tasks that "must be workflowed". Engage when the user says "workflow this", "must be workflowed", "run the bug factory", "process the open bugs", "sweep and fix the bugs", or flags a build/bug task for the full pipeline. Sweeps open issues tagged `bug` (closes already-resolved ones), then runs each surviving bug through: confirm to plan/zoom-out/blast-radius convergence loop (fresh eyes) to build (one agent per file) to test to review (blast-radius + patch-or-fix + zoom-out) to verify (computer-use + Chrome on the local Cortex instance, explicit demonstrative proof) to ship (PR to dev, babysit, test on dev, PR to main, babysit, confirm on main). One agent = one job. Proof-or-STFU. The main merge is the only human-gated step.
Audit pull requests, branches, diffs, or local source files for semantically suspicious variable, identifier, member-access, and payload-field usage. Use when checking wrong-object bugs such as product.id versus rexProduct.id, source-system identity confusion, alias erasure, mismatched payload keys, or cross-system variable mixups; optionally publishes open-PR comments or merged-PR investigation issues and hands explicit issue targets to issue-to-green-pr when publication is authorized.
Review plans, fixes, and designs before implementation so code can be built mechanically. Use before coding, contract review, spec audit, readiness checks, or post-implementation contract verification. Fails vague contracts and missing Mechanical Build Packet fields.
Use when choosing daily Helpdesk service-to-domain migration candidates, table ownership moves, write seam consolidation, domain README gaps, or A-plus architecture burn-down work before implementation.
Use when inspecting Helpdesk domains for SRP, README, write-boundary, table ownership, or service-migration opportunities and when running one selected domain refactor lane through enterprise gates, PR audits, review loops, and explicit dev merge authorization.