agentleFS
roborracleroborracle/agent-workflow-kit/skills/resume/SKILL.md

resume

Skill0 starsChanged 3 months agoMITView on GitHub

Generate a project briefing showing where you left off with recommended next steps (where was I, pick up, status update, what was I working on).

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pause, status and 9 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.
  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 7 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 15 projects that use this

  • MicrosoftSkill

    report

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts.

    Also in 7 projects that use this

  • MicrosoftSkill

    config

    Show or change TokenEconomizer's settings: turn micro-skills, tool pruning or the loop guard on or off, or tune them, for this repository or (with --global) every repository. Use when the user asks to configure, enable or disable TokenEconomizer or one of its mechanisms.

    Also in 3 projects that use this

  • sahinSkill

    execute

    Also in 4 projects that use this

  • u9401066Skill

    bug-fix

    Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.

    Also in 3 projects that use this

  • +2 more from microsoft

The file

Files
SKILL.md

Project Resume — Pick Up Where You Left Off

Pre-fetched Project State

Recent Commits

!git log --oneline --decorate -10 2>/dev/null || echo "Not a git repository"

Working Directory

!git status -sb 2>/dev/null || echo "Not a git repository"

Current Branch

!git branch --show-current 2>/dev/null

Stashed Work

!git stash list 2>/dev/null || echo "No stashes"

Recent Branches

!git branch --sort=-committerdate --format='%(refname:short) (%(committerdate:relative))' 2>/dev/null | head -10

Files Changed in Last 24h

!git log --since="24 hours ago" --name-only --pretty=format: 2>/dev/null | sort -u | grep -v '^$' || echo "None"

Open GitHub Issues

!gh issue list --state open --limit 15 --json number,title,labels,updatedAt --jq '.[] | "#\(.number) \(.title) [\(.labels | map(.name) | join(", "))] (updated: \(.updatedAt | split("T")[0]))"' 2>/dev/null || echo "No GitHub CLI or repo"

Open PRs

!gh pr list --state open --limit 10 2>/dev/null || echo "None"

Issues Closed This Week

!gh issue list --state closed --limit 10 --json number,title,closedAt --jq '.[] | "#\(.number) \(.title) (closed: \(.closedAt | split("T")[0]))"' 2>/dev/null || echo "None"


Your Task

Using the pre-fetched data above, also scan for in-progress indicators:

grep -rn "TODO\|FIXME\|HACK\|XXX" src/ app/ --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" --include="*.php" --include="*.py" --include="*.go" --include="*.rs" 2>/dev/null | head -20
grep -rn "WIP\|TEMP\|PLACEHOLDER" src/ app/ --include="*.ts" --include="*.tsx" --include="*.js" --include="*.jsx" --include="*.php" --include="*.py" --include="*.go" --include="*.rs" 2>/dev/null | head -10

Also read the project CLAUDE.md and CHANGELOG.md if they exist.

Then generate this briefing:

# Project Resume: [PROJECT NAME]
## Generated: [DATE]

## Where We Left Off
[2-3 sentence narrative. What was being worked on? Completed or mid-stream?]

## Current State
- **Branch**: [current branch, clean/dirty]
- **Uncommitted changes**: [yes/no, what files]
- **Stashed work**: [count and descriptions]
- **Open issues**: [count, highlight high-priority]
- **Open PRs**: [count and status]

## Incomplete Work
[WIP items, uncommitted changes, open feature branches, TODOs with file locations]

## Recommended Next Steps
1. **IMMEDIATE** — [unfinished work, failing tests, uncommitted changes]
2. **HIGH** — [open high-priority issues or blocked work]
3. **MEDIUM** — [technical debt, open issues]
4. **LOW** — [improvements, optimizations]

## Quick Start
[Exact commands to resume work]

Rules

  • Be specific — file names, issue numbers, branch names
  • Prioritize unfinished work over new work
  • Uncommitted changes are always priority #1
  • Flag anything broken or risky

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.