Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

debug-surface-map

Étoiles2

Forks0

Mis à jour30 mai 2026 à 16:21

Discover and document a repository's run, health, logs, traces, screenshots, network capture, state reset, and artifact bundle surfaces for agent debugging.

Installation

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.

Exécuter dans Manus

Source

Takhoffman

Takhoffman/fullselfdriving

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	debug-surface-map
description	Discover and document a repository's run, health, logs, traces, screenshots, network capture, state reset, and artifact bundle surfaces for agent debugging.

Debug Surface Map

Use this skill when a user wants a single entry point for debugging or wants to understand how an agent can observe a running app.

Discovery Order

Read AGENTS.md, README, package scripts, Makefile, justfile, Taskfile, and tool docs.
Identify the canonical run command.
Identify the canonical health check.
Identify evidence locations: logs, screenshots, traces, network captures, test reports, crash reports.
Identify state surfaces: database, filesystem, browser storage, queues, caches, external providers.
Identify reset and bundle commands.

Desired Debug Contract

debug:start -> debug:doctor -> debug:reset -> debug:bundle

Names should follow the repo's existing convention. For example:

npm run debug
just debug
make debug
cargo xtask debug
tools/debug/start

Artifact Paths

Prefer ignored repo-local paths:

.debug/
.artifacts/
tmp/debug/

Do not write evidence into tracked source directories unless the repo already has a documented artifact convention.

Plus depuis ce dépôt

même dépôt

agents-md-upgrade

Takhoffman/fullselfdriving

Create or improve AGENTS.md files so agents know the active product surface, architecture boundaries, validation commands, debug workflows, observability surfaces, isolation rules, and maintenance rules.

2026-05-302

evolution-loop

Takhoffman/fullselfdriving

Run a bounded repository improvement loop using explicit fitness criteria, small reversible mutations, validation evidence, and human approval gates.

2026-05-302

self-driving-audit

Takhoffman/fullselfdriving

Audit a repository for FullSelfDriving readiness: AGENTS.md quality, debug entry points, progressive discovery, observability, isolation, determinism, validation, safety, and evolutionary improvement readiness.

2026-05-302

name	debug-surface-map
description	Discover and document a repository's run, health, logs, traces, screenshots, network capture, state reset, and artifact bundle surfaces for agent debugging.

Debug Surface Map

Use this skill when a user wants a single entry point for debugging or wants to understand how an agent can observe a running app.

Discovery Order

Read AGENTS.md, README, package scripts, Makefile, justfile, Taskfile, and tool docs.
Identify the canonical run command.
Identify the canonical health check.
Identify evidence locations: logs, screenshots, traces, network captures, test reports, crash reports.
Identify state surfaces: database, filesystem, browser storage, queues, caches, external providers.
Identify reset and bundle commands.

Desired Debug Contract

debug:start -> debug:doctor -> debug:reset -> debug:bundle

Names should follow the repo's existing convention. For example:

npm run debug
just debug
make debug
cargo xtask debug
tools/debug/start

Artifact Paths

Prefer ignored repo-local paths:

.debug/
.artifacts/
tmp/debug/

Do not write evidence into tracked source directories unless the repo already has a documented artifact convention.