skills/session-summary/SKILL.md
Create a detailed session summary capturing actions, decisions, costs, efficiency insights, and next steps
npx skillsauth add stevefeldman/agents-skills session-summaryInstall 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.
Create a comprehensive session summary document capturing everything accomplished, decisions made, and what comes next.
Gather Session Context
Document Key Actions and Changes
git diff --stat to get a summary of files changedCapture Decisions and Rationale
Record Open Questions and Unresolved Items
Analyze Efficiency
Define Next Steps
Write the Summary File
session_{slug}_{timestamp}.md where timestamp is YYYYMMDD_HHMM# Session Summary: {Topic}
**Date:** {date}
**Turns:** {number of conversation turns}
**Cost:** {session cost if available}
## Goal
{What was the objective of this session?}
## Key Actions
- {Action 1}: {brief description}
- {Action 2}: {brief description}
- ...
## Files Changed
{Output of git diff --stat, or manual list}
## Decisions Made
| Decision | Rationale |
|----------|-----------|
| {decision} | {why} |
## Open Questions
- {Question or unresolved item}
## Efficiency Insights
- {What went well}
- {What could improve}
## Next Steps
1. {Most important next action}
2. {Second priority}
3. ...
development
Use when reviewing Dependabot alerts, npm audit findings, govulncheck output, or CVE reports on a JavaScript/Node.js or Go project — especially when triaging multiple alerts across direct and transitive dependencies to assess real-world risk and produce a remediation plan.
development
Use when a code review finding needs proof — write a focused test in JavaScript or Go that either confirms the issue is real or exposes it as over-engineering hyperbole. Trigger after code-review or code-review-skill findings are presented and evidence is requested.
development
Produce data-driven software delivery estimates by analyzing historical JIRA tickets, git activity, and engineer track records, then matching the new work against the most similar past tickets. Use this skill whenever the user asks "how long will this take", wants to estimate a piece of work, scope an epic, plan a sprint, or estimate delivery for JIRA stories or a Figma design. Also use whenever the user wants developer-to-work assignment recommendations based on history, wants to optimize an estimate by adding or reallocating engineers, or asks "what's the fastest way to ship this" or "who should work on this". Especially trigger when the user provides JIRA ticket IDs, JIRA story links, or Figma designs together with any indication of a team that will execute the work.
tools
Use when auditing an existing test suite for quality and coverage gaps, evaluating Playwright migration readiness, scoring automation against a world-class e-commerce standard, or guiding the creation of new tests. Applicable to Selenium, WebdriverIO, and Playwright suites.