agentleFS
Sign inStart free
TheKontextCoTheKontextCo/kontext-claude-plugin/skills/catch-up/SKILL.md

catch-up

Skill1 starsChanged 3 months agoMITView on GitHub

Load Kontext context for this repository or project before starting work

21 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use in-your-own-words, bro and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • drafaelSkill

    in-your-own-words

    Restate the user's goals and the problem they are trying to solve to check understanding. Manual invocation only; use when the user explicitly invokes in-your-own-words or requests this understanding check. Do not solve the task or rewrite the assistant's last answer.

    Also in 3 projects that use this

  • MicrosoftSkill

    bro

    Re-explain the previous assistant message in a much simpler way, for when the reply made you go 'bro what'. Use /bro to get a simpler version of the last answer in Plain Language + Chicago Manual of Style, with diagrams where they help.

    Also in 3 projects that use this

  • MicrosoftSkill

    blast-radius

    Assesses network dependency and shared-infrastructure exposure. Use when the user asks which services, customers, SLA policies, routes, or redundant links are affected by a network fault.

    Also in 3 projects that use this

  • photon-groveSkill

    unslop

    Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call get_my_context for the snapshot of active projects, tasks, documents, and Skills.

    line 20
  2. Very specific:

    Call get_timeline with scope: "project" and the project id — this is exactly the "what changed, where did I leave off" case the timeline …

    line 25
  3. Very specific:

    Call list_tasks for that project to get open work.

    line 28
  4. Distinctive:

    If the Space has nothing for this repository, say so in one line and offer to start a project for it.

    line 43

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Catch up

Rebuild the context for $ARGUMENTS — or, with no argument, for the repository in the current working directory.

  1. Establish what "here" is. With no argument, read the repository name and recent history:

    git log --oneline -10 && git status --short && git branch --show-current
  2. Call get_my_context for the snapshot of active projects, tasks, documents, and Skills. It is bounded — if its counts or truncation metadata indicate more, follow up with the list and search tools rather than briefing from a partial view.
  3. Find the matching workstream. If one project clearly corresponds, use it. Otherwise search_context on the repository name and the branch or feature name.
  4. Call get_timeline with scope: "project" and the project id — this is exactly the "what changed, where did I leave off" case the timeline exists for. Fall back to scope: "account" when no single project matches.
  5. Call list_tasks for that project to get open work.
  6. read_document on anything the timeline or search surfaced that looks load-bearing — a design note, a decision record, a migration plan.

Then brief the user in a few sentences:

  • What this project is and where it stands.
  • The open tasks, and which one the current branch appears to be about.
  • Decisions or constraints from Kontext that bear on the work ahead.
  • Anything in Kontext that no longer matches the code, flagged as a discrepancy rather than resolved silently.

The timeline is bounded, best-effort history. It is not an audit log and not evidence of what the user considers important — present it as "recent activity", not as priorities.

If the Space has nothing for this repository, say so in one line and offer to start a project for it. Do not create one unprompted.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free