agentleFS
Sign inStart free
aiflaredevaiflaredev/aiflare/skills/context-inject/SKILL.md

context-inject

Skill0 starsChanged 6 months agoMITView on GitHub

Inject a previous Claude Code session's saved report into the current session's context, using a sessionId copied from the AIFlare web dashboard.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before generating the report, run git log --oneline -3 to detect the language used in recent commit messages.

    line 10
  2. Very specific:

    Call the get_saved_session_report MCP tool.

    line 27
  3. Distinctive:

    If the output starts with any of the following, it is an error response — do not append any guidance and stop:

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Inject a saved report from a previous Claude Code session (produced by /summarize) into the current session's context.

Writing Language

Before generating the report, run git log --oneline -3 to detect the language used in recent commit messages. Write the entire report in that language. For example, if commit messages are in Korean, write the report in Korean. If in English, write in English.

Usage

/context-inject <sessionId>

<sessionId> is the past session's ID copied from the AIFlare web dashboard. It is NOT the current session.

Instructions

  1. Extract sessionId from $ARGUMENTS. If empty, output the following guidance and stop:

    Provide the session ID as an argument. You can copy it from the web dashboard. Usage: /context-inject <sessionId>

  2. Call the get_saved_session_report MCP tool.
    • sessionId: pass the value from step 1 verbatim.
  3. Output the string returned by the tool verbatim (no editing, summarizing, or reformatting).
  4. If the output starts with any of the following, it is an error response — do not append any guidance and stop:
    • AIFlare is not configured
    • sessionId is required
    • No saved report exists for this session
    • Error querying AIFlare:

  5. Otherwise the output is a success response (starts with ## Injected Session Report: ...). Add a blank line and then the following confirmation as the last line:

    _The report above has been injected into the current session's context. I will continue from here._
  6. For subsequent user questions, answer by referring to the injected report (especially questions about intent, rejected alternatives, or changed files).

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