update
Skill15 starsChanged 13 months agoISCView on GitHub
Morning update routine: merge Renovate PRs, rebase local work, apply chezmoi changes
- Commits and pushes
61 other projects use a version of this.
Adopted by
Most recently taken up by
- orgiggly/claude-plugintheir own version, first seen Nov 8, 2026
- ljchang/mechatheir own version, first seen Nov 8, 2026
- onetapstudiogames/1f3d9-citylifetheir own version, first seen Nov 8, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 6, 2026
- egregore-labs/egregoretheir own version, first seen Nov 6, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
Used with
Projects with it also use end, create and 10 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.
torarnvSkillend
Wrap up a work session. Updates memory files, logs decisions and lessons, appends to the session log.
Also in 3 projects that use this
MicrosoftSkillcreate
Also in 4 projects that use this
bitwize-music-studioSkilltutorial
Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.
Also in 3 projects that use this
MicrosoftSkillnote
Use this skill to record progress, partial findings, hypotheses, and page-anchored evidence while investigating a long document. Call Note aggressively — any time you read a page and confirm, narrow, or update your understanding of the user's question. Triggers include "jot that down", "save this finding", "note that page 7 says X", or (more often) implicit internal signals — you just learned something and want it recoverable later. Notes persist in the session and Review can select among them. Never paraphrase notes back from memory; write them as you go.
Also in 4 projects that use this
kv0906Skillinbox
Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.
Also in 4 projects that use this
jholhewresSkillbackup
Backup and restore — files, databases, and system backups
Also in 3 projects that use this
- +2 more from microsoft
Other versions61 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 61
- anthropics/knowledge-work-plugins★ 35ksame name
- Q00/ouroboros★ 6.3ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- patrickjaja/claude-desktop-extra★ 734same name
- me2resh/apexyard★ 542same name
- daloopa/investing★ 488same name
- TokenRollAI/cc-plugin★ 483same name
- egregore-labs/egregore★ 293same name
- k1p1l0/claude-telegram-supercharged★ 144same name
- kv0906/pm-kit★ 138same name
51 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-local-mdSkill
- allowSkill
- label-issueSkill
- miseSkill
- nvimSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 9 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 59 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 48
If the file exists, read it and check the Generated: date line.
- Distinctive: line 52
Fresh: no action needed
- Distinctive: line 62
If tracked files are modified:
- Very specific: line 73
Check CI status with gh pr checks <number>
- Distinctive: line 74
If all checks pass, prepare to merge
- Very specific: line 75
If --dry-run, just show what would be merged
- Distinctive: line 97
Read the conflicted file
- Distinctive: line 103
New additions on both sides: Keep both
- Distinctive: line 110
If not on main:
- Very specific: line 128
If --push in arguments:
- Distinctive: line 147
If mise tools are updated, they'll be installed automatically.
- Distinctive: line 171
All PRs failing: Don't merge any, report to user
- Distinctive: line 173
Catastrophic conflicts: If unable to resolve after analysis, abort rebase and report
“Common” is measured: kept by at least 6 in 10 of the 59 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.
Files
Update: Morning Maintenance
Merge Renovate PRs, rebase local work on updated main, resolve conflicts intelligently, and apply chezmoi changes.
Arguments
$ARGUMENTSOptions:
--push- Also push rebased commits to origin--dry-run- Show what would be done without making changes
Instructions
0. Check AGENTS.local.md Freshness
test -f AGENTS.local.md && echo "exists" || echo "missing"If the file exists, read it and check the Generated: date line.
- Missing: suggest "Run
/agents-local-mdto generate machine-specific context" - Older than 7 days: suggest "Run
/agents-local-md --forceto refresh machine context" - Fresh: no action needed
This is advisory only — continue the update regardless.
1. Check for Uncommitted Work
git status --shortIf tracked files are modified:
- Stash them:
git stash push -u -m "update skill: stashing before merge" - Remember to pop later
2. List and Evaluate Renovate PRs
gh pr list --author "app/renovate" --json number,title,headRefName,statusCheckRollupFor each PR:
- Check CI status with
gh pr checks <number> - If all checks pass, prepare to merge
- If
--dry-run, just show what would be merged
3. Merge Passing PRs
For each green PR:
gh pr merge <number> --squash --delete-branchCollect merged PRs for summary:
- PR number
- Package change (extract from title or diff)
4. Fetch and Rebase
git fetch origin
git rebase origin/mainWhen conflicts occur:
- Read the conflicted file
- Understand both sides:
- Incoming (Renovate/main): Usually version bumps
- Local: New packages, config changes
- Resolution strategy:
- Version conflicts: Take newer version
- New additions on both sides: Keep both
- Structural conflicts: Favor incoming (Renovate) unless it breaks local additions
- Edit the file to resolve
- Stage and continue:
git add <file> && git rebase --continue
5. Handle Feature Branches
If not on main:
git rebase mainResolve conflicts same as above.
6. Pop Stash
If stashed earlier:
git stash popResolve any conflicts using same strategy.
7. Push (if requested)
If --push in arguments:
git push origin <current-branch>8. Preview Chezmoi Changes
chezmoi diffShow a summary of what will change (not the full diff if huge).
9. Apply Chezmoi
chezmoi applyIf mise tools are updated, they'll be installed automatically.
10. Summary
Present a table:
| Action | Details |
| PRs merged | #121 (claude-code-action), #122 (codex 0.95.0) |
| Conflicts resolved | Python 3.14.2→3.14.3 + added rust 1.87.0 |
| Chezmoi applied | Python 3.14.3, codex 0.95.0 installed |
| Status | 1 commit ahead of origin/main |
Examples
/update → Merge PRs, rebase, apply (no push)
/update --push → Full update and push to origin
/update --dry-run → Preview what would happenEdge Cases
- No Renovate PRs: Skip merge step, just rebase/apply
- All PRs failing: Don't merge any, report to user
- Detached HEAD: Abort with error message
- Catastrophic conflicts: If unable to resolve after analysis, abort rebase and report
- Chezmoi template warning: Normal after config changes, not an error
- Mise tool download failures: Retry or report, but don't block rest of workflow
Philosophy
This is a single-player repository. Conflicts are rare and changes are easily revertable. The skill prioritizes automation over caution—intelligent resolution beats manual review for routine updates.
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
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.

