weekly-maintenance

Run weekly maintenance sweeps on second brain repositories with deterministic checks.

12|2|Updated Jun 8, 2026

Search Tags:#quality assurance #documentation #drift detection #maintenance #second brain #git review

Ready to run

npx skills add https://github.com/Loringtonian/second-brain-template --skill weekly-maintenance

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-maintenance
Source: https://github.com/Loringtonian/second-brain-template/tree/main/.claude/skills/weekly-maintenance
Command: npx skills add https://github.com/Loringtonian/second-brain-template --skill weekly-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill turns a sprawling second brain maintenance pass into a structured review that catches drift, stale docs, and quality issues without making the owner inspect everything manually.

Core Features & Use Cases

Runs a weekly maintenance sweep across orientation docs, TODO routing, project activity, and recent files.
Separates mechanical fixes that can be applied automatically from judgment calls that need owner input.
Uses deterministic checks plus parallel review agents to catch count drift, broken links, intent mismatch, and quality regressions.
Example: use it when you want to run weekly maintenance and get a clean list of fixes, escalations, and resolved carry-overs.

Quick Start

Use this skill when you want me to run the weekly maintenance sweep for your second brain and report the auto-fixes and judgment calls.

Frequently Asked Questions about weekly-maintenance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I detect structural drift and stale metadata in a second brain repository?▼

Detect structural drift in a second brain repository by running a weekly maintenance sweep that uses deterministic checks and parallel review agents to identify count drift, broken links, and stale metadata across orientation docs and project TODOs.

What is the best way to automate weekly maintenance and review git activity for notes?▼

Automate weekly maintenance and review git activity by running a structured sweep that separates mechanical auto-fixes from judgment calls, routing routine syncs and carry-over escalations based on recent file changes and project activity.

How do I separate automatic fixes from manual judgment calls during a documentation review?▼

Separate automatic fixes from manual judgment calls during documentation review by implementing clear action routing that applies mechanical fixes directly while escalating intent mismatches and quality regressions for owner input.

Can I use parallel review agents to catch content quality issues and intent mismatch?▼

Yes, you can use parallel review agents to catch content-quality issues and intent mismatch by deploying them alongside deterministic checks to scan recent files and project activity for broken links and quality regressions.

What are the limitations of running a deterministic weekly maintenance sweep?▼

A limitation of running a deterministic weekly maintenance sweep is that while it catches mechanical drift and broken links automatically, it must escalate intent mismatches and quality regressions as judgment calls requiring owner input.