> Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.
npx skills add https://github.com/NicholasSpisak/second-brain --skill second-brain-lint
Health-check the wiki and report issues with actionable fixes.
Run all checks below, then present a consolidated report.
Scan all wiki pages for [[wikilink]] references. For each link, verify the target page exists. Report any broken links.
# Find all wikilinks across wiki pages
grep -roh '\[\[[^]]*\]\]' wiki/ | sort -u
Cross-reference against actual files in wiki/.
Find pages with no inbound links — no other page references them via [[wikilink]].
For each .md file in wiki/sources/, wiki/entities/, wiki/concepts/, wiki/synthesis/:
[[Page Name]]Read pages that share entities or concepts and look for conflicting claims. Flag when:
Cross-reference source dates with wiki content. Flag when:
Scan for [[wikilinks]] that point to pages that don't exist yet. These are topics the wiki mentions but hasn't given their own page. Assess whether they warrant a page.
Find pages that discuss the same topics but don't link to each other. Look for:
Verify wiki/index.md is complete and accurate:
wiki/sources/, wiki/entities/, wiki/concepts/, wiki/synthesis/ has an index entryBased on the wiki's current coverage, suggest:
Present findings grouped by severity:
For each finding, include:
Ask the user:
> "Found N errors, N warnings, and N info items. Want me to fix any of these?"
If the user agrees, fix issues and report what changed.
Append to wiki/log.md:
Found N errors, N warnings, N info items. Fixed: [list of fixes applied].
/second-brain-ingest — process new sources into wiki pages/second-brain-query — ask questions against the wikiUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Take nicholasspisak/second-brain-lint from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.