skills.rest
danielkhigay
danielkhigayCOMMUNITY
Explore all skills by this author →
GitHub

manage-history

List, inspect, and delete obsolete dev sessions via the development API.

Updated Feb 19, 2026
Search Tags:#testing#api#cleanup#dev#session-history#bulk-delete
One-click install
npx skills add https://github.com/danielkhigay/gaz --skill manage-history
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: manage-history
Source: https://github.com/danielkhigay/gaz/tree/main/.claude/skills/manage-history
Command: npx skills add https://github.com/danielkhigay/gaz --skill manage-history

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspect and clean up session history in development environments by listing sessions by status, inspecting past sessions, or bulk-deleting old test sessions.

Core Features & Use Cases

  • List sessions by status (round_1, round_1_5, round_2, locked, tabled, close_failed) and sort by creation date.
  • Inspect a session's state via its status endpoint to review the id, status, and deadline fields.
  • Bulk-delete sessions to maintain a clean dev workspace by removing terminal-state or all sessions.

Quick Start

List terminal-state sessions and bulk-delete them.

Frequently Asked Questions about manage-history

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

FAQPage Schema
How do I bulk-delete old dev sessions using the development API?▼

You can bulk-delete old dev sessions by listing sessions by status and removing terminal-state or all sessions via the development API endpoints. Requires endpoints for /api/dev/sessions and /api/dev/sessions/:id/status with proper authentication.

What dev session statuses can I filter by when cleaning up session history?▼

You can filter dev session history by statuses such as round_1, round_1_5, round_2, locked, tabled, and close_failed. Sessions are sorted by creation date to help you identify and purge obsolete records efficiently.

How do I inspect a specific session's state before deleting it?▼

You inspect a specific session's state by calling its status endpoint (/api/dev/sessions/:id/status) to review the id, status, and deadline fields. This allows you to verify session details before performing any cleanup or deletion operations.

Does this session cleanup method require any specific environment setup?▼

Session cleanup requires a development environment where sessions accumulate statuses and exposes endpoints for /api/dev/sessions and /api/dev/sessions/:id/status. Proper authentication must be configured to access these endpoints for listing, inspecting, and deleting sessions.

What's the best way to maintain a clean dev workspace by purging test sessions?▼

The best way to maintain a clean dev workspace is to regularly list terminal-state sessions sorted by creation date and bulk-delete them. This removes obsolete test sessions that accumulate statuses like locked, tabled, or close_failed.

Related Skills

Explore More Software Engineering Skills→
danielkhigaydanielkhigay

manage-sessions

Automate dev session lifecycle operations via /api/dev/sessions endpoints.

Community
Advanced
Atrium-HermesAtrium-Hermes

Janitor

Delete stale .notify-*, .pending-notify-temp, and .outputs artifacts by TTL.

Community
Intermediate
nrwlnrwl
27

await-polygraph-ci

Monitor CI pipeline statuses across repositories in a Polygraph session.

Official
Advanced
GDSDNGDSDN
3

test-as-user

Emulate authenticated database users to test RLS policies in psql.

Community
Advanced