skills.rest
gaabscps
gaabscpsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ship

Delete terminal FEAT and DISC session traces after human confirmation.

1|Updated May 3, 2026
Search Tags:#terminal#confirmation#session-cleanup#cross-squad#sdd-discovery#runtime-trace
One-click install
npx skills add https://github.com/gaabscps/ai-squad --skill ship-gaabscps
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ship
Source: https://github.com/gaabscps/ai-squad/tree/main/shared/skills/ship
Command: npx skills add https://github.com/gaabscps/ai-squad --skill ship-gaabscps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removes a finished session's runtime trace after human confirmation, ensuring the workspace remains clean and avoiding accidental retention of runtime data.

Core Features & Use Cases

  • Cross-squad cleanup for FEAT and DISC sessions by deleting terminal session traces only after explicit confirmation.
  • Guards against active work by ensuring current_phase is terminal (done, paused, escalated) before deletion.
  • Provides a clear pre-deletion summary and a human-in-the-loop confirmation step to prevent unintended data removal.

Quick Start

Confirm a terminal session cleanup by providing the spec_id (e.g., FEAT-NNN or DISC-NNN) and confirming the action to remove its runtime trace.

Frequently Asked Questions about ship

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely clean up terminal session runtime traces after completion?▼

To clean up terminal session runtime traces, you must enforce a precondition check on session.yml to verify the session reached a terminal state, then securely remove the .agent-session directory after explicit human confirmation.

What happens if I try to delete a runtime trace for an active session?▼

Deleting an active session's runtime trace is blocked by a precondition check on session.yml, ensuring current_phase is terminal (done, paused, escalated) before allowing secure removal of the .agent-session directory.

How do I remove an .agent-session directory for a finished FEAT or DISC session?▼

To remove an .agent-session directory, provide the spec_id for a finished FEAT or DISC session, review the pre-deletion summary, and submit explicit confirmation to securely delete the associated runtime trace.

Can I automate workspace cleanup without a human-in-the-loop confirmation step?▼

Workspace cleanup cannot be automated without confirmation, as securely removing the .agent-session trace requires a human-in-the-loop confirmation step to prevent unintended data removal.

When should I use cross-squad session cleanup to clear runtime data?▼

Use cross-squad session cleanup to clear runtime data when FEAT or DISC sessions have reached a terminal state, ensuring the workspace remains clean and avoiding accidental retention of finished runtime traces.

Does terminal session cleanup require any external dependencies or component installations?▼

Terminal session cleanup requires no external dependencies or component installations, relying solely on internal precondition checks against session.yml and human confirmation to securely remove the .agent-session directory.

Related Skills

Explore More Software Engineering Skills→
michael-conradmichael-conrad

finishing-a-development-branch

Verify a finished feature branch is committed, tested, reviewed, and pushed before PR.

Community
Advanced
OrcaQubitsOrcaQubits
35

webmcp-user-interaction

Integrate user confirmation prompts into AI agent tool execution.

Official
Intermediate
deerawandeerawan
1

gsd-autonomous

Automate milestone phase completion by running discuss-to-execute workflows sequentially.

Community
Advanced
dbowm91dbowm91

shell_session

Creates, lists, updates and deletes in-memory shell and terminal session metadata for codegg agent architecture.

Community
Intermediate