st0nefish/summarize
plugins-claude/session/skills/summarize/SKILL.md
Summarize the current repo state. Triggers on "what was I working on?", "session status", "catch me up", or when returning to active work. Returns a paragraph plus categorized file/detail bullets.
development
Updated May 15, 2026
$ install --global
skillsauthnpx skillsauth add st0nefish/claude-toolkit summarizeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 15, 2026, 4:36 AM9.2s1 file scanned
SKILL.md
- user-invocable:
- true
- name:
- summarize
- description:
- >-
- allowed-tools:
- Task, Bash, Read
Summarize
Use one script call as the source of truth, then summarize with an agent.
Steps
-
Run:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/sitrep -
If output says
is_git_repo: false, report that a summary cannot be generated outside a git repository. -
Otherwise, invoke the Task tool (
agent_type: general-purpose) and provide only this script output as input context. -
Return exactly this structure:
<paragraph summarizing the situation> * <major change category one summary> * <file 1> * <file 1 detail 1> * <file 1 detail 2> * <file 2> * <file 2 detail 1> * <file 2 detail 2> * <major change category two summary> * <file 3> * <file 3 detail 1>
Rules
- Trust script sections as authoritative (do not run extra git commands unless script fails).
- Include committed + staged + unstaged + untracked file changes when present.
- Group files under 2-5 major categories (examples: "New functionality", "Refactors", "Fixes", "Docs/metadata").
- If output shows
clean: truewith no active branches, return only a short paragraph and no bullet list.
Related Skills
st0nefish/session-start
development
VerifiedTrustedCommunity
Start work from your description — explore the codebase and plan
1SKILL.mdUpdated May 27, 2026
st0nefish/session-orchestrate
data-ai
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 27, 2026
st0nefish/session-issue
tools
VerifiedTrustedCommunity
Browse open issues, pick one, and start work on it
1SKILL.mdUpdated May 27, 2026
st0nefish/git-cli
tools
VerifiedTrustedCommunity
Interact with GitHub and Gitea issue trackers and CI systems. List and show issues, file bugs, comment on issues or PRs, list and show pull requests, and fetch CI run logs — all from any repo context without leaving the session.
1SKILL.mdUpdated May 8, 2026