agentleFS
Sign inStart free
ARCASSystemsARCASSystems/FounderOS/skills/history/SKILL.md

history

Skill7 starsChanged 19 days agoMITView on GitHub

Show the founder their saved versions as readable dated events, wrapping git log so they never read a SHA. Trigger on "what changed", "show my history", "version history", "what did I save", "show my saved versions", "what have I changed", or any plain request to see past versions. Renders newest first, grouped by day. Handles a fresh repo with no saved versions and a shallow clone gracefully instead of erroring.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup.

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.
  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 4

    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:

    If core/identity.md does not exist, stop with: Founder OS not set up here.

    line 19
  2. Very specific:

    If git is not installed or the folder has no .git/ directory (a ZIP install that has not graduated yet), do not error.

    line 21
  3. Very specific:

    Run python scripts/caveman_git.py history.

    line 25
  4. Distinctive:

    If the script says nothing is saved yet (a fresh install with no user versions, including a fresh clone with only the upstream version, or …

    line 27
  5. Distinctive:

    Read-only. This verb never changes anything.

    line 35
  6. Distinctive:

    No SHAs in what you show the founder.

    line 36
  7. Distinctive:

    No em dashes or en dashes.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 12 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

History

Runs on: local-exec - runs a local script; on a cloud surface I read the results, I do not run it.

Show the founder their saved versions as readable, dated events. Wraps git log so they never read a SHA. Read-only.

Pre-flight

  • If core/identity.md does not exist, stop with: Founder OS not set up here. Run /founder-os:setup first.
  • If scripts/caveman_git.py does not exist, stop with: Version control helper not found. Run /founder-os:update to install it.
  • If git is not installed or the folder has no .git/ directory (a ZIP install that has not graduated yet), do not error. Show what the session-change tracker knows instead (python scripts/session_changes.py --print), then say: That is this session's changes. For a full permanent timeline, say "own my history" and I will set it up for you.

Procedure

  1. Run python scripts/caveman_git.py history. For the full list rather than the recent slice, use --full. For a specific count, use --limit N.
  2. Relay the output as the script prints it: dated events, grouped by day, newest first. Do not add SHAs or git jargon.
  3. If the script says nothing is saved yet (a fresh install with no user versions, including a fresh clone with only the upstream version, or a shallow clone), relay that plainly and offer: say "save my work" to record the first version.

Runtime honesty

This verb runs a local script. On a surface that cannot run a script, say so and offer to read whatever history the founder can paste; you cannot generate the live history there.

Rules

  • Read-only. This verb never changes anything.
  • No SHAs in what you show the founder. Dates and plain summaries only.
  • No em dashes or en dashes. Hyphens only.

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