smithers-bug

File a smithers bug report to bug.smithers.sh; with --run it attaches the run's status, error, and last ~50 events (secrets scrubbed). Run `smithers bug --help` for usage details.

Aller à l'installation

Dépôt: smithersai/smithers
Dernière activité de la source: 13 juillet 2026 à 04:41
Langue détectée de SKILL.md: anglais
Étoiles: 404
Forks: 50

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/smithersai/smithers --skill smithers-bug

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

smithers

Drive Smithers, a durable control plane for long-running coding agents, from Claude Code. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work ('orchestrate agents', 'run a workflow', 'implement this and review it', 'keep iterating until tests pass', 'plan then build') or anything needing retries, approvals, replay, or evals across multiple AI steps. YOU (Claude) run Smithers on the user's behalf; it is not a GUI the human clicks. HARD RULE 0, if `SMITHERS_INSIDE_RUN` is set in your environment you are ALREADY a worker agent inside a Smithers node, so never invoke the Smithers CLI or MCP tools to launch or steer a run, just do the node's task directly with your ordinary tools; every rule below applies only when it is unset. HARD RULE 1, right-size the route FIRST, handle ANY clear single-goal ask directly, even a large repo-wide one, and reserve a full workflow for work that genuinely needs ordered stages, durability, approvals, loops, or reuse; never author a multi-no

2026-08-27

smithers

Drive Smithers, a durable control plane for long-running coding agents, from Codex. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work ("orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build") or anything needing retries, approvals, replay, or evals across multiple AI steps. YOU (Codex) run Smithers on the user's behalf; it is not a GUI the human clicks. HARD RULE 0: if `SMITHERS_INSIDE_RUN` is set in your environment you are ALREADY a worker agent inside a Smithers node — never invoke the Smithers CLI or MCP tools to launch or steer a run, just do the node's task directly with your ordinary tools; every rule below applies only when it is unset. HARD RULE 1: right-size the route FIRST, handle a clear well-scoped single-goal task directly, and reserve a full workflow for work that genuinely needs ordered stages, durability, approvals, loops, or reuse. A workflow that runs long, fans out, or pauses on

2026-08-27

smithers

Drive Smithers, a durable control plane for long-running coding agents. Use when the user wants multi-step, long-running, crash-safe, or human-in-the-loop agent work: "orchestrate agents", "run a workflow", "implement this and review it", "keep iterating until tests pass", "plan then build", or anything that needs retries, approvals, replay, or evals across multiple AI steps. YOU (the agent) run Smithers on the user's behalf; it is not a GUI the human clicks. HARD RULE 0: if `SMITHERS_INSIDE_RUN` is set in your environment you are ALREADY a worker agent inside a Smithers node, so never invoke the Smithers CLI or MCP tools to launch or steer a run; do the node's task directly with your ordinary tools. Everything below applies only when it is unset. You are otherwise an ORCHESTRATOR: run long-running, multi-step, or background work *through* Smithers, not through your own ad-hoc subagents; spend your time observing the run and reporting. Also governs DELIVERABLE SHAPE even when no workflow is involved: a user

2026-08-27

Tout voir dans ce dépôt

Flag	Type	Description
`--run`	`string`	Attach this run's workflow name, status, error, and recent events to the report
`--title`	`string`	Bug title (derived from the run's error when omitted)
`--body`	`string`	Bug description body
`--endpoint`	`string`	Bug endpoint URL (default https://bug.smithers.sh/api/bugs; the SMITHERS_BUG_ENDPOINT env var takes precedence)

Flag	Type	Description
`--run`	`string`	Attach this run's workflow name, status, error, and recent events to the report
`--title`	`string`	Bug title (derived from the run's error when omitted)
`--body`	`string`	Bug description body
`--endpoint`	`string`	Bug endpoint URL (default https://bug.smithers.sh/api/bugs; the SMITHERS_BUG_ENDPOINT env var takes precedence)

name	smithers-bug
description	File a smithers bug report to bug.smithers.sh; with --run it attaches the run's status, error, and last ~50 events (secrets scrubbed). Run `smithers bug --help` for usage details.
requires_bin	smithers
command	smithers bug

smithers-bug

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

smithers bug

Options

Plus depuis ce dépôt

smithers bug

Options