mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-10-09 03:17:54 +00:00

fix: rename all remaining built-in-shadowing skill names and harden the last cp1252-fatal scripts (#885 , #969 follow-through)

Round-2 sweep after re-auditing all 15 reported issues against the merged dev:

- #885 generalized: the original fix only renamed self-improving-agent's
  status/review, but three more plugins shipped skills whose bare names
  shadow Claude Code built-ins. Renamed with the same convention:
  playwright-pro init/review -> pw-init/pw-review, agenthub init/status ->
  hub-init/hub-status, autoresearch-agent status/resume -> ar-status/
  ar-resume. All command references (/pw: /hub: /ar:), docs, audit records,
  harness manifests, and mirror trees/indexes updated; the flat mirror
  namespace no longer collides on 'status'. New scripts/check_skill_names.py
  gate (wired into ci-quality-gate.yml as blocking) fails CI on any future
  bare reserved name; rule added to SKILL-AUTHORING-STANDARD.md.
- #969 follow-through: five more scripts print box-drawing characters that
  cannot exist in cp1252 (api_scorecard, api_linter,
  breaking_change_detector, humanizer_scorer, content_scorer) — same
  guarded UTF-8 reconfigure applied; all smoke-tested under a forced
  legacy encoding.

Verified: check_skill_names (incl. negative test), check_plugin_json,
check_paths, derive_counters, check_dual_publish, smoke_scripts (634/634),
0 broken mirror symlinks.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qgc6RYXWJPr5oW9DHU7zR4

2026-08-21 08:38:50 +00:00

2.5 KiB

Raw Permalink Blame History

AgentHub — Claude Code Instructions

This plugin enables multi-agent collaboration. Spawn N parallel subagents that compete on the same task, evaluate results, and merge the winner.

Commands

Use the /hub: namespace for all commands:

/hub:hub-init — Create a new collaboration session (task, agent count, eval criteria)
/hub:spawn — Launch N parallel subagents in isolated worktrees (supports --template)
/hub:hub-status — Show DAG state, agent progress, and branch status
/hub:eval — Rank agent results by metric or LLM judge
/hub:merge — Merge the winning branch, archive losers
/hub:board — Read/write the agent message board
/hub:run — One-shot lifecycle: init → baseline → spawn → eval → merge

How It Works

You (the coordinator) orchestrate N subagents working in parallel:

/hub:hub-init — define the task, number of agents, and evaluation criteria
/hub:spawn — launch all agents simultaneously via the Agent tool with isolation: "worktree"
Each agent works independently in its own git worktree, commits results, writes to the board
/hub:eval — compare results (run eval command per worktree, or LLM-judge diffs)
/hub:merge — merge the best branch into base, tag and archive the rest

Key Principle

Parallel competition. Immutable history. Best result wins.

Agents never see each other's work. Every approach is preserved in the git DAG. The coordinator evaluates objectively and merges only the winner.

Agents

hub-coordinator — Dispatches tasks, monitors progress, evaluates results, merges winner. This is YOUR role as the main Claude Code session.

Branch Naming

hub/{session-id}/agent-{N}/attempt-{M}

Message Board

Agents communicate via .agenthub/board/ markdown files:

dispatch/ — task assignments from coordinator
progress/ — status updates from agents
results/ — final result summaries from agents

When to Use

User says "try multiple approaches" or "have agents compete"
Optimization tasks where different strategies might win
Code generation where diversity of solutions helps
Competing content drafts — 3 agents write blog posts or landing page copy, LLM judge picks best
Research synthesis — agents explore different source sets or analytical frameworks
Process optimization — agents propose competing workflow improvements
Feature prioritization — agents build different RICE/ICE scoring models
Any task that benefits from parallel exploration

2.5 KiB Raw Permalink Blame History