Skip to content

NagareNegishi/DJ-App / .claude/skills/session-wrapup

session-wrapup

Verified

Close out a working session: update `docs/progress.md`, report uncommitted and unpushed work, and list the session's decisions and open threads. Read-only on git — never commits, stages, or pushes.

Session Wrapup

Close out the current session: run the three steps below in order. Never commit, stage, or push — all git checks are read-only.

1. Update docs/progress.md

Record what this session completed:

  • Read docs/progress.md first and match its existing entry format exactly — heading style, date format, level of detail.
  • If the file does not exist, create it with a short dated entry in a minimal format.
  • Record completed work only; in-progress work belongs in the open-threads report (step 3).
  • Write entries following the human-writing skill.

2. Report git state

Read-only checks:

  • git status — list uncommitted changes; when the conversation makes it clear, group them as session work versus unrelated or pre-existing.
  • git log @{upstream}..HEAD --oneline — list unpushed commits. If the branch has no upstream, say so instead of guessing.
  • Leave commit decisions to the user; suggest a commit message if the uncommitted work forms one coherent change.

3. List open threads and decisions

From this session's conversation, report:

  • Decisions made — choices with lasting effect (approach picked, alternative rejected, convention adopted), each in one line with the reason.
  • Open threads — work started but unfinished, questions raised but not answered, TODOs mentioned in passing, follow-ups promised.
  • Suggested next step — the single most useful thing to start the next session with.

Skip empty categories rather than padding them.

Output

Present steps 2 and 3 in chat as the wrapup report. Write no file other than docs/progress.md.

rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall