Read-only analysis skill that finds broken [[wiki-links]] by
extracting link targets from all markdown files and verifying
each target file exists via Glob. Groups broken links by source
file and suggests close matches for misspelled targets.
Handles edge cases: heading anchors, block references, aliases,
embedded images, template placeholders, and external links.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Grep-based search skill with zero dependencies — works in any vault
without indexes, plugins, or setup. Groups results by directory
(Daily Notes, Goals, Projects, etc.) and suggests related wiki-linked
notes found in matching files.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Add TaskGet to allowed-tools in daily, weekly, goal-tracking skills
- Rename "Progress Tracking" sections to "Task-Based Progress Tracking"
- Add pseudo-YAML TaskCreate examples with subject, description, activeForm
- Add explicit Dependencies sections with addBlockedBy syntax
- Add reminder to mark tasks in_progress/completed using TaskUpdate
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Integrate Claude Code's task tools (TaskCreate, TaskUpdate, TaskList)
into skills and agents to provide spinner updates during multi-step
operations like morning routines, weekly reviews, and batch processing.
- Add task tools to allowed-tools in daily, weekly, goal-tracking skills
- Add task tools to 4 agents (inbox-processor, weekly-reviewer, etc.)
- Create task-tracking.md rule with naming conventions and best practices
- Document progress patterns with concrete spinner output examples
- Update CLAUDE.md and README.md with progress visibility feature
Task tools are session-scoped progress indicators that complement (not
replace) the existing markdown checkbox system in daily notes.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Five improvements to the setup wizard:
1. Relative path handling:
Convert relative paths to absolute paths after user input to prevent
failures when `claude init` changes the working directory.
2. Git push error handling:
Detect actual branch name and show real errors instead of suppressing
them and falling back to non-existent `master`.
3. Interactive push recovery:
When push fails (e.g., remote has existing content), offer interactive
options: force push with confirmation, or skip with manual command.
4. GitHub Actions setup after failed push:
Only copy workflow files if push succeeds to avoid confusion.
5. OAuth token setup guidance:
Replace cryptic "Remember to add CLAUDE_CODE_OAUTH_TOKEN" with:
- Step-by-step instructions
- Direct link to token documentation
- Link to repository secrets page
- Option to open setup page in browser
Co-authored-by: eiszazel <eiszazel@users.noreply.github.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* v2.1: Unify skills and slash commands pattern
Following the new Claude Code standard where skills and slash commands
are merged into a single unified pattern:
- Convert commands to skills: /daily-workflow, /weekly-review, /push, /onboard
- Each skill has SKILL.md with frontmatter (name, description, allowed-tools)
- Skills can be invoked with /skill-name OR auto-discovered by Claude
- Remove deprecated .claude/commands/ directory
- Update all documentation to reference new unified pattern
- Update agents to reference skills instead of commands
- Update CLAUDE.md with unified skills table
This aligns with Claude Code 2.1+ where skills and slash commands
share the same features and invocation patterns.
* Simplify skill names: daily-workflow → daily, weekly-review → weekly
Rename verbose skill folders and names to shorter, cleaner invocations:
- daily-workflow/ → daily/ (invoked with /daily)
- weekly-review/ → weekly/ (invoked with /weekly)
Update all references across documentation, agents, and skill files
to use consistent short command names.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
Update all references from docs.anthropic.com/en/docs/claude-code
to code.claude.com/docs after documentation site migration.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Core structure with README, LICENSE, and .gitignore
- Complete vault template with Goals, Daily Notes, Projects, and Templates
- Cascading goal system (3-year → yearly → monthly → weekly)
- Claude Code integration with custom slash commands
- GitHub Actions workflow for mobile integration
- Comprehensive documentation (setup, customization, workflows, troubleshooting)
- Automation scripts for setup (Unix/Mac and Windows)
- Example content showing system usage
- Self-documenting templates with inline instructions
Ready for users to clone and customize for their personal knowledge management needs.
