Skip to content
Back to skills

Update Tears

ASecurity

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

  • 18 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 7, 2026
ai-agentsbashgit

Works with

  • cli

Security analysis

A100/100

Scanned November 7, 2026

npx -y skills add jamie8johnson/cqs --skill update-tears --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Update Tears?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Update Tears
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jamie8johnson-update-tears/badge)](https://www.skillsdirectory.com/skills/jamie8johnson-update-tears)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: update-tears
description: Update PROJECT_CONTINUITY.md and notes.toml with current session state. Use proactively before context compaction or when switching tasks.
disable-model-invocation: false
---

# 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:

```bash
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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.