maintenance
Skill9 starsChanged 9 months agoMITView on GitHub
Session 5のメンテナンス(記憶整理・統計更新・長期記憶化・embedding再構築・working_memory整理・todo整理)をするとき → このスキルを最初に読む
- Commits and pushes
18 other projects use a version of this.
Adopted by
Most recently taken up by
- spleenteo/maestrotheir own version, first seen Nov 16, 2026
- maxwell2732/claudecode-research-harness-workflowtheir own version, first seen Nov 15, 2026
- adelrodriguez/skillstheir own version, first seen Nov 15, 2026
- erikdarlingdata/PerformanceMonitortheir own version, first seen Nov 11, 2026
- bekalpaslan/promptlinetheir own version, first seen Nov 8, 2026
- anatolykoptev/piter-writer-packtheir own version, first seen Nov 8, 2026
Used with
Projects with it also use memory and release.
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.
GoogleSkillmemory
Records and appends every user-agent customer support interaction to the memory.md log in the workspace.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- Chachamaru127/claude-code-harness★ 3.2ksame name
- erikdarlingdata/PerformanceMonitor★ 536same name
- pipecat-ai/gradient-bang★ 420same name
- hyperlist/feishu-multi-agent★ 273same name
- erikdarlingdata/PerformanceStudio★ 245same name
- everruns/everruns★ 67same name
- maxwell2732/claudecode-research-harness-workflow★ 42same name
- everruns/yolop★ 18same name
- JPeetz/agent-skills★ 17same name
- bekalpaslan/promptline★ 13same name
8 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 repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .claude/skills/latest-apis/CLAUDE.mdCLAUDE.md
- ayumu-emailSkill
- browserSkill
- calendarSkill
- cameraSkill
- claude-historySkill
- creationSkill
- discordSkill
- feedsSkill
- identitySkill
- latest-apisSkill
- lifeSkill
- project-structureSkill
- readingSkill
- recallSkill
- security-reviewSkill
- smart-homeSkill
- speakSkill
- twitterSkill
- voice-chatSkill
- websiteSkill
The file
Files
メンテナンススキル
Session 5(メンテナンスセッション)で実行するタスク。
注意: テスト、セキュリティチェック等はcronで自動化できる。gateway/cron.json で設定。
Session 5 チェックリスト
1. Embedding再構築
uv run infra/generate_embeddings.py記憶検索の精度に直結。knowledgeが増えたらインデックス更新が必要。
2. working_memory.md整理(最重要)
目標: 500行以下
サイズ確認:
wc -l memory/working_memory.md && wc -l memory/todo.mdRecent Sessions削減
- 3日分だけ残す(今日、昨日、一昨日)
- それ以前は
memory/mid-term/YYYY-MM-WX.mdに要約して移動
週間スケジュール更新
- 古い日付を削除(1週間以上前)
継続的な情報の整理
- 1ヶ月以上古い情報は削除
- 完了したタスクは削除
3. todo.md整理
目標: 150行以下、アクティブなタスクのみ
- 完了済み(
[x])→ Archivedに移動 or 削除 - 不要タスク → 削除
- 重要タスクを上に
- 曖昧なタスクを具体化
4. 記憶の長期化
Recent Sessionsを見て、重要な学びを移動:
- 技術的な学び →
memory/knowledge/topic-name.md - システム変更 →
CLAUDE.md - 新しい人物情報 →
memory/knowledge/person-name.md
5. フォルダ構造監査
プロジェクトルートやツール群のフォルダ構造を確認し、散らかっていないかチェック。
- 一時ファイルの削除
- 不要な実験ファイルの整理
- working_memory.md 500行超・todo.md 150行超の検出
6. コミット&プッシュ
git add -A
git commit -m "YYYY-MM-DD Session 5/5: メンテナンス完了"
git pushcronで自動化できるタスク例
| cron名 | 時刻 | 内容 |
| daily-tests | 3:00 | pytest実行 |
| daily-security | 3:30 | セキュリティチェック |
| daily-cleanup | 5:00 | フォルダ整理 |
| morning-info | 8:30 | 情報収集 |
設定: gateway/cron.json
メンテナンスのメンテナンス
Session 5自体が機能しているか、毎回確認:
- このSKILL.mdは読まれているか? → gateway/message_builder.pyに指示があるか
- todo.md/goals.jsonは毎回読まれているか? → CLAUDE.mdに明記されているか
- cronジョブは正常に動いているか? → 直近のcron実行ログを確認
- 「時間厳しい」を言い訳にしない
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.

