agentleFS
jamie8johnsonjamie8johnson/cqs/.claude/skills/update-tears/SKILL.md

update-tears

Skill18 starsChanged 5 months agoMITView on GitHub

Update PROJECT_CONTINUITY.md and notes.toml with current session state. Use proactively before context compaction or when switching tasks.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    Open Issues: Keep current — check if any listed issues were closed

    line 26
  2. Distinctive:

    Architecture: Update version, test count, or structural changes if they happened

    line 28
  3. Distinctive:

    Add notes for any surprises from this session via CLI:

    line 32
  4. Distinctive:

    Sentiment is DISCRETE: only use -1, -0.5, 0, 0.5, 1.

    line 42
  5. Distinctive:

    Don't log activity — git history has that

    line 46
  6. Very specific:

    Keep PROJECT_CONTINUITY.md concise — it's read on every resume

    line 48
  7. Distinctive:

    Check for dirty files with git status and note uncommitted work in Pending Changes

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Update Tears

Capture current session state to survive context compaction.

Files to update

PROJECT_CONTINUITY.md

Update these sections:

  1. Right Now: What you're actively working on. Include:
    • Task description and date
    • Branch name
    • What's done in this session
    • What still needs to happen
    • Any open PRs
  2. Parked: Threads to revisit later (moved from Right Now when switching tasks)
  3. Open Issues: Keep current — check if any listed issues were closed
  4. Architecture: Update version, test count, or structural changes if they happened

docs/notes.toml

Add notes for any surprises from this session via CLI:

cqs notes add "note text" --sentiment 0.5 --mentions file.rs,concept
  • Bugs that were non-obvious (sentiment: -1 or -0.5)
  • Patterns that worked well (sentiment: 0.5 or 1)
  • Observations worth remembering (sentiment: 0)

Sentiment is DISCRETE: only use -1, -0.5, 0, 0.5, 1.

Rules

  • Don't log activity — git history has that
  • Focus on state that would be lost: what's in progress, what decisions were made, what's blocked
  • Keep PROJECT_CONTINUITY.md concise — it's read on every resume
  • Check for dirty files with git status and note uncommitted work in Pending Changes

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.