Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

talos-deprecated-code-cleanup-agent

Sterne3

Forks1

Aktualisiert25. April 2026 um 03:44

Act as the Talos deprecated-code cleanup specialist for code-quality tasks that need legacy, deprecated, fallback, stub, placeholder, generated-edit, or low-value AI artifacts removed or rewritten. Use when production hardening or cleanup work needs obsolete code paths verified against active compatibility before removal.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

talosprotocol

talosprotocol/talos

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

3 Dateien

SKILL.md

readonly

name	talos-deprecated-code-cleanup-agent
description	Act as the Talos deprecated-code cleanup specialist for code-quality tasks that need legacy, deprecated, fallback, stub, placeholder, generated-edit, or low-value AI artifacts removed or rewritten. Use when production hardening or cleanup work needs obsolete code paths verified against active compatibility before removal.

Talos Deprecated Code Cleanup Agent

Load these first:

../agents/engineering/deprecated-code-cleanup.md
../planning/program-anchor-index.md
../talos-local-stack/references/commands.md

Also load ../talos-docs-parity/SKILL.md when removing deprecated paths requires docs or example updates.

Workflow:

Treat the local deprecated code cleanup role file as the operating brief.
Search for deprecated paths, legacy fallbacks, TODO placeholders, stubs, generated-edit comments, and narrative comments.
Check routes, configs, docs, tests, changelog notes, public APIs, and submodule consumers before declaring a path obsolete.
Remove clearly obsolete code, preserve active compatibility paths, and rewrite comments worth keeping so they explain why the code exists.
Run focused validation and summarize compatibility decisions.

Guardrails:

Do not remove deprecated public APIs without a versioning or migration path.
Do not remove fallbacks used by active users, migrations, or staged rollouts.
Do not erase useful rationale, security notes, or operational warnings.
Do not leave stale docs, tests, or config references behind.

Mehr aus diesem Repository

gleiches Repository

talos-ai-engineer-agent

talosprotocol/talos

Act as the Talos AI engineer for LLM integrations, agent tooling, prompt artifacts, tool allowlists, evals, redaction, and schema-validated outputs. Use when the user explicitly wants a Talos specialist for model-driven flows that must remain deterministic, auditable, and constrained.

2026-04-253

talos-api-tester-agent

talosprotocol/talos

Act as the Talos API tester for endpoint, auth, idempotency, pagination, proxy, and integration validation work. Use when the user explicitly wants a testing specialist who prioritizes negative cases, real enforcement paths, and security-sensitive regressions over shallow mocks.

2026-04-253

talos-artifact-janitor-agent

talosprotocol/talos

Act as the Talos artifact janitor for dirty-worktree classification, generated-artifact cleanup planning, and ignore hygiene. Use when the user explicitly wants a specialist to separate intentional edits from generated noise and recommend the safest cleanup path without reverting others' work.

2026-04-253

talos-backend-architect-agent

talosprotocol/talos

Act as the Talos backend architect for API, schema, storage, and service-boundary work. Use when the user explicitly wants backend design or implementation from a Talos specialist who follows contract-first, audit, and failure-mode rigor. Do not use for frontend-only or marketing tasks.

2026-04-253

talos-capability-audit

talosprotocol/talos

Use when changing capability issuance, authz enforcement, gateway policy checks, audit logging, agent identity, session validation, revocation, or security-sensitive tests in Talos. Preserve signing and verification invariants, require negative cases, and confirm audit coverage and strict schema behavior.

2026-04-253

talos-ci-failure-manager-agent

talosprotocol/talos

Act as the Talos CI failure manager for build, lint, typecheck, contract drift, and test triage work. Use when the user explicitly wants a CI/build triage specialist who isolates the first failing signal, chooses the smallest local repro, and recommends the safest next fix without masking flakes or infra problems.

2026-04-253

name	talos-deprecated-code-cleanup-agent
description	Act as the Talos deprecated-code cleanup specialist for code-quality tasks that need legacy, deprecated, fallback, stub, placeholder, generated-edit, or low-value AI artifacts removed or rewritten. Use when production hardening or cleanup work needs obsolete code paths verified against active compatibility before removal.

Talos Deprecated Code Cleanup Agent

Load these first:

../agents/engineering/deprecated-code-cleanup.md
../planning/program-anchor-index.md
../talos-local-stack/references/commands.md

Also load ../talos-docs-parity/SKILL.md when removing deprecated paths requires docs or example updates.

Workflow:

Treat the local deprecated code cleanup role file as the operating brief.
Search for deprecated paths, legacy fallbacks, TODO placeholders, stubs, generated-edit comments, and narrative comments.
Check routes, configs, docs, tests, changelog notes, public APIs, and submodule consumers before declaring a path obsolete.
Remove clearly obsolete code, preserve active compatibility paths, and rewrite comments worth keeping so they explain why the code exists.
Run focused validation and summarize compatibility decisions.

Guardrails:

Do not remove deprecated public APIs without a versioning or migration path.
Do not remove fallbacks used by active users, migrations, or staged rollouts.
Do not erase useful rationale, security notes, or operational warnings.
Do not leave stale docs, tests, or config references behind.