agentleFS
Sign inStart free
aiflaredevaiflaredev/aiflare/skills/session-compare/SKILL.md

session-compare

Skill0 starsChanged 6 months agoMITView on GitHub

Compare two Claude Code sessions side by side, then save the comparison report to the server.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tstapler/dotfiles★ 8same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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. Distinctive:

    All report content MUST be written in formal report style.

    line 14
  3. Very specific:

    Call the get_session_compare MCP tool to retrieve session comparison data.

    line 20
  4. Very specific:

    If one session ID is provided as an argument ($ARGUMENTS contains one value), pass it as sessionId1 (current session vs specified session).

    line 21
  5. Very specific:

    If two session IDs are provided (space-separated), pass them as sessionId1 and sessionId2.

    line 22
  6. Distinctive:

    If no argument is given, omit both (current session vs previous session will be used automatically).

    line 23
  7. Very specific:

    Call the save_session_compare_report MCP tool to save the report to the server.

    line 38

≈ “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

Generate a session comparison report.

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.

Writing Style

All report content MUST be written in formal report style. Do not use conversational or casual tone.

  • O: "Work continuity between the two sessions was confirmed.", "AuthService.kt was modified in both sessions."
  • X: "Looks like work continued across sessions.", "AuthService.kt got changed in both."

Instructions

  1. Call the get_session_compare MCP tool to retrieve session comparison data.
    • If one session ID is provided as an argument ($ARGUMENTS contains one value), pass it as sessionId1 (current session vs specified session).
    • If two session IDs are provided (space-separated), pass them as sessionId1 and sessionId2.
    • If no argument is given, omit both (current session vs previous session will be used automatically).
  2. Based on the returned data, generate a comparison report in English with the following sections:
    • Title: A one-sentence summary of the comparison (include both session names)
    • Session 1 Summary: Session name, date, commit count, tag distribution, changed files, key decisions
    • Session 2 Summary: Same structure as Session 1
    • Comparison Analysis:
      • Overlapping files (files changed in both sessions)
      • New files in Session 2 (files only in the later session)
      • Whether this is continued work or a direction change
      • Tag shift analysis (did the type of work change?)
    • Conclusion: 1-2 sentences on work continuity and any notable direction changes
  3. Display the generated report to the user.
  4. Call the save_session_compare_report MCP tool to save the report to the server.
    • sessionId1: The first session ID from the comparison data
    • sessionId2: The second session ID from the comparison data
    • title: The title generated above
    • content: The full report content (Markdown)
  5. Display a save confirmation message.

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