Index of every page on this site: llms.txt
All skills
elithrar avatar

/summarize-work

@eb4f994
by Matt Silverlockelithrar/dotfiles226 stars
16
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/elithrar/dotfiles/summarize-work

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈67 tokens for metadata: the name and description. ≈365 when used: this file. ≈1.1k more on demand in 2 files.

Description uses 3.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈270 characters, or 3.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 alert2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is designed to summarize work history by querying a local OpenCode server or a local SQLite database. It follows good security practices, such as using read-only database access and URL encoding for parameters. However, like all skills that process past conversation logs, it is theoretically susceptible to indirect prompt injection if the logs contain malicious instructions.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    2/2 files flagged

Signed by skilld at eb4f994. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 3 months ago

README badge

README badge for elithrar/dotfiles/summarize-work