agentleFS
leonsong09leonsong09/session-wrap/SKILL.md

session-wrap

Skill9 starsChanged 8 months agoMITView on GitHub

Use when the user wants to wrap up the current coding session, summarize the current session before ending work, document learnings, decide what to commit, or says 总结会话, 会话总结, 收尾, 会话收尾, 结束会话, 总结本次会话.

14 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to close out the current coding session in a way that is easy to resume later.

    line 11
  2. Distinctive:

    Do not output a chronological 流水账.

    line 17
  3. Distinctive:

    Do not claim work is completed unless there is evidence in the session, git status, or validation output.

    line 18
  4. Distinctive:

    If the user asks to write files, commit, or update docs, summarize first and then confirm the action.

    line 19
  5. Distinctive:

    Default to the current session.

    line 25
  6. Distinctive:

    If the repository state is not available, say so explicitly and continue with the session evidence you do have.

    line 44
  7. Distinctive:

    If there were no meaningful code changes, say that clearly instead of inventing成果.

    line 56
  8. Distinctive:

    Keep this section concise and operational.

    line 67
  9. Distinctive:

    When relevant, finish with:

    line 71
  10. Distinctive:

    Do not auto-commit. Recommend commit timing only when there is enough evidence.

    line 77

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

Session Wrap Skill

Overview

Use this skill to close out the current coding session in a way that is easy to resume later. Focus on what was actually finished, what is still open, what was learned, and what should happen next.

Core Rules

  • Scope is the current session unless the user explicitly asks for a broader range.
  • Prioritize outcomes, decisions, learnings, and follow-up actions over process chatter.
  • Do not output a chronological 流水账.
  • Do not claim work is completed unless there is evidence in the session, git status, or validation output.
  • If the user asks to write files, commit, or update docs, summarize first and then confirm the action.

Workflow

Step 1: Confirm scope

Default to the current session. If the user already gave a clear wrap-up request, do not ask extra questions.

Clarify only when needed:

  • current session only or also include earlier sessions
  • whether to include commit advice
  • whether to produce a handoff note or just a chat summary

Step 2: Inspect the working tree

Collect the minimum evidence needed to summarize the session accurately.

Recommended commands:

git status --short
git diff --stat
git log --oneline -n 10

If the repository state is not available, say so explicitly and continue with the session evidence you do have.

Step 3: Summarize completed work

Summarize by workstream instead of by timestamp.

Preferred structure:

  • 本次完成
  • 关键决策
  • 涉及文件 / 模块
  • 已做验证

If there were no meaningful code changes, say that clearly instead of inventing成果.

Step 4: Extract learnings and open items

Capture the parts that matter for the next session:

  • new findings
  • mistakes avoided or lessons learned
  • known risks
  • unfinished tasks
  • blockers or dependencies

Keep this section concise and operational.

Step 5: Offer next actions and commit guidance

When relevant, finish with:

  • suggested next steps
  • whether a commit is appropriate now
  • a possible commit message direction
  • whether additional verification is still needed

Do not auto-commit. Recommend commit timing only when there is enough evidence.

Recommended Output Shape

## 本次会话总结

### 已完成
- ...

### 关键决策
- ...

### 涉及文件 / 模块
- ...

### 验证情况
- 已验证:...
- 未验证:...

### 经验与风险
- ...

### 下一步建议
- ...

When to Use

  • 用户说“总结会话”
  • 用户说“收尾”或“会话收尾”
  • 当前会话已经完成一段明确工作,需要压缩成可复用总结
  • 需要为下一次继续工作准备 handoff

When Not to Use

  • 用户要的是“今天所有会话”的汇总,而不是当前会话
  • 用户要的是纯 commit 日报
  • 当前会话几乎没有实际工作内容,只是简单问答

In those cases, prefer a daily summary or research-note style skill instead.

Quality Checklist

Before responding, verify:

  • Summary is scoped to the current session unless user asked otherwise
  • Completed work is grouped by workstream, not by timeline
  • Validation is reported honestly
  • Risks and unfinished items are explicit
  • No fake completion, fake commit readiness, or fake verification claims

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.