Skip to content

chore: GUT skills UI dead code tree (~160 lines, 5 files) #2224

@alexey-pelykh

Description

@alexey-pelykh

Problem

The skills UI in the web dashboard is completely dead code. The "skills" tab does not exist in the Tab union (navigation.ts), so the render branch never executes. All skill controller functions are replaced with no-op stubs.

Dead Code Inventory

ui/src/ui/app-render.ts

  • Line 12: loadAgentSkills no-op stub
  • Lines 63-67: 5 no-op stubs (installSkill, loadSkills, saveSkillApiKey, updateSkillEdit, updateSkillEnabled)
  • Line 87: renderSkills no-op stub
  • Lines 906-929: Dead state.tab === "skills" render branch (with @ts-expect-error)
  • Lines 570-577, 602-603, 613, 633, 729-732, 736-762: Dead skills wiring in agents view

ui/src/ui/app.ts

  • Lines 236-238: Dead agentSkillsLoading, agentSkillsError, agentSkillsReport @State() properties
  • Lines 343-349: Dead skillsLoading through skillMessages @State() properties (7 total)
  • Line 61: Dead SkillMessage type stub

ui/src/ui/app-view-state.ts

  • Line 13: Dead SkillMessage type stub
  • Lines 160-162: Dead agentSkills* type properties
  • Lines 240-246: Dead skills* type properties (7 total)

ui/src/ui/views/agents.ts

  • Lines 60-62, 67, 86: Dead skill props in agents view interface

ui/src/ui/types.ts

  • Lines 636-640: SkillStatusReport type (check for other consumers before removing)

Acceptance Criteria

  • No @ts-expect-error referencing skills in app-render.ts
  • No no-op skill stubs in app-render.ts (lines 12, 63-67, 87)
  • No dead skills render branch in app-render.ts
  • No dead skills*/agentSkills* state properties in app.ts
  • No dead skills*/agentSkills* type properties in app-view-state.ts
  • Build passes, tests pass

Context

Part of @ts-expect-error fork-sync remediation audit. Suggestion file: .tmp/suggest-fix10-skills-ui-gut.md.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions