agentleFS
Sign inStart free
abhaylaabhayla/claude-best-practices/.claude/skills/continue/SKILL.md

continue

Skill9 starsChanged 7 months agoMITView on GitHub

Resume work from a previous session. Reads continuation state, workflow progress, git state, and recent test evidence to produce a briefing with suggested next action. Use when starting a new conversation or returning after a break.

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dependency-watch, perform-task and 8 more.

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

    dependency-watch

    Audit Telegram Desktop dependencies on freshly fetched origin/dev for releases and security fixes, including upstream lag and backport candidates in patched forks. Use for the scheduled dependency monitor or an explicitly requested dependency report.

    Also in 5 projects that use this

  • telegramdesktopSkill

    perform-task

    Resolve, start or resume, implement, review, test, and publish exactly one existing ai-tdesktop task by short slug or full dated id, including rare blocked retries and split-required results. Use when the user invokes $perform-task or /perform-task with a known task name, or when the continue scheduler delegates one selected task. Runs standard review lenses with fast applicability bailouts and selects task-specific domain and evidence instruments without selecting additional work.

    Also in 5 projects that use this

  • JerovinoSkill

    process-inbox

    Processes tasks.md inbox items by triaging each one to its proper location in the vault

    Also in 5 projects that use this

  • raineSkill

    rebase

    Rebase the current branch with smart conflict resolution.

    Also in 6 projects that use this

  • lepinkainenSkill

    code-health

    Analyze codebase health - large files, test coverage gaps, duplicate code, dead/legacy code, and documentation issues. Use when asked to scan, audit, or assess code quality, find refactoring targets, or identify technical debt.

    Also in 3 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Read the following (skip any that don't exist):

    line 30
  2. Distinctive:

    MUST NOT modify any files — this skill is strictly read-only

    line 77
  3. Distinctive:

    MUST keep the briefing concise — under 30 lines

    line 78
  4. Distinctive:

    MUST include a specific suggested next action

    line 79
  5. Very specific:

    MUST check for saved session files in .claude/sessions/ before falling back to git-only briefing

    line 80

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

Continue — Resume Previous Work

Resume work from where the last session left off.

Critical: This skill is read-only — MUST NOT modify any files. For restoring a saved session checkpoint, use /start-session instead. For a full handover document, use /handover.

STEP 1: Gather State

Read the following (skip any that don't exist):

  1. Continuation docs — Look for CONTINUE_PROMPT.md, docs/CONTINUE_PROMPT.md, or similar handoff documents
  2. Git state — git status, git log --oneline -5, git stash list
  3. Recent changes — git diff --stat HEAD~3..HEAD
  4. Open issues — gh issue list --assignee @me --state open --limit 5 (if gh is available)
  5. Task/TODO files — Check for TODO.md, tasks.md, or similar
  6. Saved sessions — Check if .claude/sessions/ exists with .md files. If found, note the most recent session and suggest: "Saved session found: {name} ({date}). Use /start-session to restore full context, or continue with this general briefing."

STEP 2: Assess Priority

Based on gathered state, determine the highest priority action:

StatePriorityAction
Uncommitted changesHighReview and commit or continue work
Failing testsHighRun tests, fix failures
Open PR with review commentsHighAddress review feedback
In-progress featureMediumContinue implementation
Stashed changesMediumReview stash and apply or drop
No clear stateLowAsk user what to work on

STEP 3: Briefing

Present a concise briefing:

## Session Briefing

### Current State
[One-line summary]

### Recent Activity
- [Last 3-5 meaningful changes]

### Pending Work
1. [Highest priority item]
2. [Next priority]

### Suggested Next Action
> [Specific actionable suggestion]

CRITICAL RULES

  • MUST NOT modify any files — this skill is strictly read-only
  • MUST keep the briefing concise — under 30 lines
  • MUST include a specific suggested next action
  • MUST check for saved session files in .claude/sessions/ before falling back to git-only briefing

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