Agent skill

Summarize Work

by elithrar in elithrar/dotfiles

Summarize OpenCode session history into work recaps, commit messages, or PR descriptions.

MITAuto-check passedDevelopment

Install Summarize Work

skills CLI
$ npx skills add elithrar/dotfiles --skill summarize-work -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install elithrar/dotfiles summarize-work --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/elithrar/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/summarize-work .claude/skills/summarize-work && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
summarize-work
GitHub stars
202
Token cost
~439 tokens
SKILL.md length
210 words
Files
3 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Summarize OpenCode session history into work recaps, commit messages, or PR descriptions.

  • A summary needs past sessions
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Cross-project history
  • Ordinary commits and summaries fully supported by the current conversation do not need this skill

What it does

Summarize Work is an agent skill from elithrar/dotfiles. Summarize OpenCode session history into work recaps, commit messages, or PR descriptions. Use when a summary needs past sessions or cross-project history; ordinary commits and summaries fully supported by the current conversation do not need this skill.

Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/evals.json` and `references/api.md`).

It sits in Development, covering Pull requests and Commit messages. The repository describes itself as: dotfiles for my macOS & Linux environments ⌨️. The licence is MIT.

When your agent uses it

  • A summary needs past sessions
  • Cross-project history
  • Ordinary commits and summaries fully supported by the current conversation do not need this skill

Example prompts

  • “/summarize-work”

What it can do on your machine

Read from SKILL.md and the folder at commit 26e8a4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Summarize Work loads about 439 tokens when it runs, and up to ~1.3k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 210 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~439
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from elithrar/dotfiles at commit 26e8a4b, republished under its MIT licence (© elithrar). 210 words, ~439 tokens.

Download SKILL.mdSave it as .claude/skills/summarize-work/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
summarize-work
description
Summarize OpenCode session history into work recaps, commit messages, or PR descriptions. Use when a summary needs past sessions or cross-project history; ordinary commits and summaries fully supported by the current conversation do not need this skill.

OpenCode work summaries

Use the requested project and time range. Default to the current project; expand across projects only when requested or needed to answer an explicit correction. Use the user's timezone for time boundaries.

For the current session, use the conversation and relevant git state without querying OpenCode. For past sessions, read references/api.md to discover the configured server and retrieve only relevant history. Do not silently drop short sessions or truncate their substantive content; even one message can record an important fix.

Reconcile session claims with the relevant diff, commits, or file state when available. Resolve the actual base branch or upstream rather than assuming origin/main or origin/master. Distinguish planned, attempted, implemented, tested, and merged work. Todos and an assistant's success claim alone are not proof of completion.

Write the requested recap, commit message, or PR description. Explain why the change mattered and what it accomplished. Group cross-project work by project and omit empty categories. Keep the output proportional to the meaningful changes, and follow the user's requested structure.

Exclude secrets and sensitive transcript data. If history cannot be retrieved, summarize the available evidence and state the coverage gap. Do not infer missing work or ask for a service setup before completing a summary the visible context already supports.

© elithrar, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .agents/skills/summarize-work of elithrar/dotfiles.

  • SKILL.md
  • evals/evals.json
  • references/api.md

Open the folder on GitHubat commit 26e8a4b

Compare with similar skills

Summarize Work next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Summarize Work compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Summarize Work this skillelithrar/dotfiles202—~439Automated safety check: PassMIT
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Git Workflow and Versioningaddyosmani/agent-skills103k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Emoji Commit ConventionsbaptisteArno/typebot.io11k—~424Automated safety check: PassCustom licence

Similar skills

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    103k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Emoji Commit Conventions

    baptisteArno/typebot.io

    Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.

    11k GitHub stars~424 tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commit And PR Messages

    superplanehq/superplane

    Write Git commit messages and pull request titles/descriptions using the Chris Beams / Tim Pope conventions (subject/body split, ~50-char subject, imperative mood, why-not-how body) plus ASD-STE100…

    7.7k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed

More from elithrar/dotfiles

All 12 skills in this repo
  • Prompt Engineer

    elithrar/dotfiles

    Audit and revise system prompts, developer instructions, tool descriptions, and reusable LLM prompt templates.

    202 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Code Reviewer

    elithrar/dotfiles

    Review a specified code change for actionable defects. An agent skill from elithrar/dotfiles.

    202 GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Cut Ready

    elithrar/dotfiles

    Prepare or review CAD and vector artwork for physical fabrication, cutting, printing, or machining.

    202 GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Logging Sucks

    elithrar/dotfiles

    Design or review structured application logging, canonical request events, correlation, redaction, and sampling.

    202 GitHub stars~720 tokensUpdated today
    Auto-check passed
  • Motronic

    elithrar/dotfiles

    Diagnose Porsche Carrera 3.2 Bosch Motronic faults and interpret DME ROMs or calibration changes.

    202 GitHub stars~753 tokensUpdated today
    Auto-check passed
  • Neo Industrial Design

    elithrar/dotfiles

    Design or restyle web interfaces in the user's neo-industrial or editorial-brutalist style.

    202 GitHub stars~940 tokensUpdated today
    Auto-check passed

Categories

Questions about Summarize Work

What does Summarize Work do?

Summarize OpenCode session history into work recaps, commit messages, or PR descriptions. Summarize Work is an agent skill from elithrar/dotfiles. Summarize OpenCode session history into work recaps, commit messages, or PR descriptions.

When should I use Summarize Work?

Summarize Work fits situations like: A summary needs past sessions; cross-project history; ordinary commits and summaries fully supported by the current conversation do not need this skill.

How do I install Summarize Work in Claude Code?

Run `npx skills add elithrar/dotfiles --skill summarize-work -a claude-code`. Or copy the skill folder (.agents/skills/summarize-work in elithrar/dotfiles) into .claude/skills/summarize-work in your project. Claude Code loads it when a task matches its description.

How do I install Summarize Work in Codex?

Run `npx skills add elithrar/dotfiles --skill summarize-work -a codex`. Or copy the skill folder (.agents/skills/summarize-work in elithrar/dotfiles) into .agents/skills/summarize-work in your project. Codex loads it when a task matches its description.

Can I use Summarize Work in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add elithrar/dotfiles --skill summarize-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/summarize-work, .gemini/skills/summarize-work, .github/skills/summarize-work and .opencode/skills/summarize-work in your project.

What does Summarize Work need to run?

SKILL.md names no scripts, command-line tools or credentials: Summarize Work is instructions for the agent only.

Does Summarize Work access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Summarize Work safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Summarize Work use?

Summarize Work is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Summarize Work use?

About 439 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 858 tokens, read only when the agent opens those files.

What are the alternatives to Summarize Work?

Skills that share tags, products or a category with Summarize Work: PR Finalize Review (microsoft/garnet, 12k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars) and Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Summarize Work?

elithrar (a GitHub user) maintains it in elithrar/dotfiles, which has 202 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 7, 2026.

Source: elithrar/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.