plugins-claude/session-history-analyzer/skills/history-status/SKILL.md
Show analysis state — analyzed vs pending session counts per project
npx skillsauth add st0nefish/claude-toolkit history-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Show the current state of session history analysis.
Get analysis state summary:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.sh summary
Discover all available sessions:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/discover-sessions.sh
Cross-reference to compute pending counts per project. Present a status card:
Last analysis: <date or "never">
Total analyzed: <N> sessions
Pending: <N> sessions across <N> projects
Per project:
<slug>: <analyzed>/<total> sessions
...
If there are pending sessions, suggest running /session-history-analyzer:history-analyze.
development
Start work from your description — explore the codebase and plan
data-ai
Multi-phase, multi-agent feature workflow: spec → plan → refine → divide → execute → review. Invoke when the user escalates a session-start/session-issue flow to orchestration, or asks to run a non-trivial feature (multiple files, design ambiguity, cross-cutting concerns, correctness-critical paths) through the full multi-agent workflow. For small fixes, prefer session-start.
tools
Browse open issues, pick one, and start work on it
tools
Review, clean up, and open a PR to finalize the work