Automated summary
This skill prepares a session or handoff summary by reviewing Git logs, recent file changes, and pipeline status, then produces a structured document.
Strengths
- Automates creation of comprehensive handoff documents
- Leverages Git history and pipeline status for reliable data
- Generates a timestamped file that is easy to locate
Limitations
- Depends on the quality of commit messages
- Only captures versioned changes, not unrecorded discussions
- Works only if the /status command is available
Use this skill before a long break, a contributor handoff, or to document project progress.
Do not use it for informal updates or when the Git history is too large without prior filtering.
Security analysis
SafeThe skill only instructs to review version control logs, modified files, and pipeline status, then generate a plain-language summary written locally to a session_logs directory. There are no destructive actions, network calls, or data exfiltration.
No concerns found
How this analysis is madeExamples
Prepare a session handoff summary for the last 7 days, including git log and pipeline status.After merging PR #42, create a handoff summary focusing on changes in the src/ and docs/ directories.Prepare a co-author or future-session summary. Review: (1) Git log since the last handoff (or last 7 days if no prior handoff). (2) Any files modified recently. (3) Current pipeline status (run /status internally). Produce a plain-language summary covering: what changed, what outputs were regenerated, what to review, open questions. Write to session_logs/YYYY-MM-DD_handoff.md (create session_logs/ if needed).
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/prepare-a-handoff-summary-mrwakecq/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/prepare-a-handoff-summary-mrwakecq' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/prepare-a-handoff-summary-mrwakecq/download' --output '.skill-downloads/prepare-a-handoff-summary-mrwakecq/SKILL.md.part' && mv '.skill-downloads/prepare-a-handoff-summary-mrwakecq/SKILL.md.part' '.skill-downloads/prepare-a-handoff-summary-mrwakecq/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/prepare-a-handoff-summary-mrwakecq/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Supabase Docs Authoring
Documentation
Write, edit, and review Supabase documentation content including guides, tutorials, reference docs, and partials. Follow style guides and MDX/TOML validation rules.
Create Architecture Decision Record
Documentation
Create a new Architecture Decision Record with sequential numbering, register it in the AgentDB graph, and link related ADRs.
Plan update with deep research
Documentation
Updates a plan document by launching parallel subagents to analyze a topic across all compiler passes, then consolidates findings into the plan doc.