Not in the top 1,000 by GitHub stars
ViryaZheng/wrap-skill
A Claude Code skill that consolidates scattered project markdown files into a single canonical CLAUDE.md, with a pinned PROGRESS block at the top.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
plugins/wrap/skills/wrap/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
64a95bce950e → 64a95bce950e
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 64a95bce950e
No earlier version was observed for comparison.
View on GitHubAdd to my skills
Verified commit 64a95bce950efdafe91d0f527cf73646a21a2139
git clone --filter=blob:none --no-checkout https://github.com/ViryaZheng/wrap-skill.git .hotskills/viryazheng-wrap-skill && git -C .hotskills/viryazheng-wrap-skill checkout --detach 64a95bce950efdafe91d0f527cf73646a21a2139
# Copy each selected skill directory from .hotskills/viryazheng-wrap-skill into .claude/skills/<skill-name>/55GitHub stars
-1star in 7 days
1skill in this repository
0commits in 30 days
Heat
0.2- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- wrap
plugins/wrap/skills/wrap
How it works
wrap
When your agent uses it
Session wrap-up: consolidates every descriptive markdown file (README.md, AGENTS.md, HANDOFF.md, docs/*) into ONE canonical CLAUDE.md, then reconciles it against the current code state so a fresh session or new teammate can pick up immediately. CLAUDE.md keeps a mandatory PROGRESS block at the top answering two questions: where are we now and what's the next concrete action. Trigger when the user says: "wrap", "wrap up", "/wrap", "tidy docs", "sync docs", "update docs", "archive", "this phase is done", or the Chinese equivalents "收尾", "同步文档", "整理文档", "整理一下", "更新文档", "存档", "梳理一下", "这阶段做完了". A bare "tidy" / "整理" with prior dev context counts. Do not under-trigger.
What it loads into context
Frontmatter
208 tokensAlways available to the agent
SKILL.md
2,390 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Mindset — Why This Skill Exists
- Three Non-Negotiable Principles
- Execution Flow
- Anti-Patterns (Don't)
- Cross-Platform
Files
../../../../.claude-plugin/marketplace.jsonasset696 bytes../../.claude-plugin/plugin.jsonasset445 bytesSKILL.mdcore9,607 bytesSKILL.mdcore9,607 bytes
Read SKILL.md
# wrap — Single-File Project State Maintenance
You are a **project documentation editor**. Each time you are invoked, fold every scattered descriptive markdown file in the project into a single `CLAUDE.md`, and make sure it aligns with the current truth of the code. After this skill runs, that one file is the entry point for whoever picks the project up next.
## Core Mindset — Why This Skill Exists
**The conversation context evaporates. Code persists. `CLAUDE.md` is the bridge.**
The moment the user runs `/clear`, starts a new session, hands off to a teammate, or just comes back tomorrow, *every* fact that lived only in chat — decisions made, dead ends hit, half-finished thoughts, the "what's next" you both agreed on five minutes ago — is **gone**. Code and git history survive; conversation does not.
`wrap` exists to fight that loss. Its job is to take whatever was discussed, decided, or discovered in this session and **land it in `CLAUDE.md`** so the next Claude (or human) can pick up the work without re-asking, re-deriving, or re-breaking things. Every rule below — PROGRESS pinned at the top, merge-and-delete the scattered docs, brevity over completeness — exists to serve that one goal.
**The test of a good wrap:** if you `/clear` right now and a fresh session opens this project with only `CLAUDE.md` to read, can it continue the work? If no, the wrap isn't done.
Skills included
- wrap
Repository facts
- License
- MIT
- Created
- May 5, 2026
- Last pushed
- May 17, 2026
- Forks
- 4
- Open issues
- 0
- Project activity
- Slowing
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 4, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 1 note
plugins/wrap/skills/wrap/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- No dangerous shell commands
- 8 network referencesin 2 files: .claude-plugin/marketplace.json:12 plugins/wrap/.claude-plugin/plugin.json:7
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
Show all 8 signals by file
.claude-plugin/marketplace.json
- Network accessline 12
"version": "1.1.0", "license": "MIT", "homepage": "https://github.com/recomby-ai/wrap-skill", - Network accessline 13
"license": "MIT", "homepage": "https://github.com/recomby-ai/wrap-skill", "repository": "https://github.com/recomby-ai/wrap-skill", - Network accessline 14
"homepage": "https://github.com/recomby-ai/wrap-skill", - Network accessline 15
"repository": "https://github.com/recomby-ai/wrap-skill",
plugins/wrap/.claude-plugin/plugin.json
- Network accessline 7
}, "license": "MIT", "homepage": "https://github.com/recomby-ai/wrap-skill", - Network accessline 8
"license": "MIT", "homepage": "https://github.com/recomby-ai/wrap-skill", "repository": "https://github.com/recomby-ai/wrap-skill", - Network accessline 9
"homepage": "https://github.com/recomby-ai/wrap-skill", - Network accessline 10
"repository": "https://github.com/recomby-ai/wrap-skill",
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
No combined signals at this commit.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Manifest .claude-plugin/marketplace.json | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md plugins/wrap/skills/wrap/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md plugins/wrap/skills/wrap/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md plugins/wrap/skills/wrap/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md plugins/wrap/skills/wrap/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md plugins/wrap/skills/wrap/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
