v2.1: Unify skills and slash commands pattern (#5)

* 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>
This commit is contained in:
Bill Allred
2026-01-12 11:57:37 -08:00
committed by GitHub
parent 3d66b2121a
commit fa10141e9e
16 changed files with 689 additions and 969 deletions

View File

@@ -6,7 +6,7 @@
A complete personal knowledge management system that combines Obsidian's powerful note-taking with Claude Code's AI assistance. Go from zero to a fully functional PKM in 15 minutes or less. A complete personal knowledge management system that combines Obsidian's powerful note-taking with Claude Code's AI assistance. Go from zero to a fully functional PKM in 15 minutes or less.
**v2.0** - Now with hooks, custom agents, skills, and modular rules. **v2.1** - Unified skills pattern (skills and slash commands merged), hooks, agents, and rules.
## ✨ Features ## ✨ Features
@@ -17,10 +17,10 @@ A complete personal knowledge management system that combines Obsidian's powerfu
- **🔄 Version Controlled** - Never lose a thought with automatic Git backups - **🔄 Version Controlled** - Never lose a thought with automatic Git backups
- **🎨 Fully Customizable** - Adapt templates and structure to your needs - **🎨 Fully Customizable** - Adapt templates and structure to your needs
### AI-Powered (v2.0) ### AI-Powered (v2.1)
- **⚡ Unified Skills** - Skills and slash commands merged (`/daily`, `/weekly`, `/push`, `/onboard`)
- **🪝 Hooks** - Auto-commit on save, session initialization - **🪝 Hooks** - Auto-commit on save, session initialization
- **🤖 Custom Agents** - Note organizer, weekly reviewer, goal aligner, inbox processor - **🤖 Custom Agents** - Note organizer, weekly reviewer, goal aligner, inbox processor
- **⚡ Skills** - Auto-discovered capabilities for vault ops, goal tracking, daily workflows
- **📏 Modular Rules** - Path-specific conventions for markdown, productivity, projects - **📏 Modular Rules** - Path-specific conventions for markdown, productivity, projects
- **🧠 Output Styles** - Productivity Coach for accountability - **🧠 Output Styles** - Productivity Coach for accountability
- **📊 Status Line** - Vault stats in terminal (note count, inbox, uncommitted changes) - **📊 Status Line** - Vault stats in terminal (note count, inbox, uncommitted changes)
@@ -80,16 +80,18 @@ Your Vault/
├── .claude-plugin/ ├── .claude-plugin/
│ └── plugin.json # Plugin manifest │ └── plugin.json # Plugin manifest
├── .claude/ ├── .claude/
│ ├── commands/ # Slash commands (/daily, /weekly, /push, /onboard) │ ├── agents/ # Custom AI agents
│ ├── agents/ # Custom AI agents (NEW)
│ │ ├── note-organizer.md │ │ ├── note-organizer.md
│ │ ├── weekly-reviewer.md │ │ ├── weekly-reviewer.md
│ │ ├── goal-aligner.md │ │ ├── goal-aligner.md
│ │ └── inbox-processor.md │ │ └── inbox-processor.md
│ ├── skills/ # Auto-discovered capabilities (NEW) │ ├── skills/ # Unified skills (invoke with /skill-name)
│ │ ├── obsidian-vault-ops/ │ │ ├── daily/ # /daily - Create daily notes, routines
│ │ ├── goal-tracking/ │ │ ├── weekly/ # /weekly - Weekly review process
│ │ ── daily-workflow/ │ │ ── push/ # /push - Git commit and push
│ │ ├── onboard/ # /onboard - Load vault context
│ │ ├── goal-tracking/ # Auto: Track goal progress
│ │ └── obsidian-vault-ops/ # Auto: Vault file operations
│ ├── hooks/ # Event automation (NEW) │ ├── hooks/ # Event automation (NEW)
│ │ ├── session-init.sh │ │ ├── session-init.sh
│ │ └── auto-commit.sh │ │ └── auto-commit.sh

View File

@@ -7,7 +7,7 @@ Make this PKM system truly yours. This guide covers everything from simple tweak
2. [Template Modifications](#template-modifications) 2. [Template Modifications](#template-modifications)
3. [Folder Structure](#folder-structure) 3. [Folder Structure](#folder-structure)
4. [Tag System](#tag-system) 4. [Tag System](#tag-system)
5. [Claude Commands](#claude-commands) 5. [Skills (Unified Pattern)](#skills-unified-pattern)
6. [Output Styles](#output-styles) 6. [Output Styles](#output-styles)
7. [Workflow Automation](#workflow-automation) 7. [Workflow Automation](#workflow-automation)
8. [Theme and Appearance](#theme-and-appearance) 8. [Theme and Appearance](#theme-and-appearance)
@@ -249,19 +249,30 @@ Use multiple tags for powerful filtering:
#work #priority/high #energy/high #context/office #work #priority/high #energy/high #context/office
``` ```
## Claude Commands ## Skills (Unified Pattern)
### Creating Custom Commands In Claude Code v2.1+, skills and slash commands are unified. All capabilities are now skills that can be invoked with `/skill-name` or auto-discovered by Claude.
#### Example: Book Notes Command ### Creating Custom Skills
Create `.claude/commands/book.md`:
Create a new skill directory with a `SKILL.md` file:
#### Example: Book Notes Skill
Create `.claude/skills/book-notes/SKILL.md`:
```markdown ```markdown
# Book Notes Creator ---
name: book-notes
description: Create book notes with metadata. Use when starting a new book or organizing reading notes.
allowed-tools: Read, Write, Edit, Glob
user-invocable: true
---
# Book Notes Skill
Creates a new book note with metadata and structure. Creates a new book note with metadata and structure.
## Usage ## Usage
claude code /book "Book Title" "Author" Invoke with `/book-notes` or ask Claude to create a book note.
## What it does ## What it does
1. Creates note in Resources/Books/ 1. Creates note in Resources/Books/
@@ -270,17 +281,24 @@ claude code /book "Book Title" "Author"
4. Links to reading list 4. Links to reading list
``` ```
#### Example: Meeting Notes Command #### Example: Meeting Notes Skill
Create `.claude/commands/meeting.md`: Create `.claude/skills/meeting-notes/SKILL.md`:
```markdown ```markdown
# Meeting Notes ---
name: meeting-notes
description: Create formatted meeting notes with action items. Use before or after meetings.
allowed-tools: Read, Write, Edit
user-invocable: true
---
# Meeting Notes Skill
Creates formatted meeting notes with action items. Creates formatted meeting notes with action items.
## Usage ## Usage
claude code /meeting "Meeting Title" Invoke with `/meeting-notes` or ask Claude to create meeting notes.
## Template ## Template Structure
- Date/Time - Date/Time
- Attendees - Attendees
- Agenda - Agenda
@@ -289,20 +307,14 @@ claude code /meeting "Meeting Title"
- Follow-up - Follow-up
``` ```
### Modifying Existing Commands ### Modifying Existing Skills
#### Daily Command for Different Schedules #### Daily Workflow for Different Schedules
Edit `.claude/commands/daily.md`: Edit `.claude/skills/daily/SKILL.md` to customize:
```javascript - Daily notes folder location
// For night shift workers - Template path
const DAILY_NOTES_TIME = "18:00"; // 6 PM start - Date format preferences
- Time block structure
// For early risers
const MORNING_ROUTINE_START = "05:00";
// For parents
const INCLUDE_FAMILY_SECTION = true;
```
## Output Styles ## Output Styles
@@ -396,15 +408,22 @@ Edit `.claude/output-styles/coach.md` to adjust the coaching approach:
### Morning Routine Automation ### Morning Routine Automation
Create `.claude/commands/morning.md`: Create `.claude/skills/morning-routine/SKILL.md`:
```markdown ```markdown
# Morning Routine ---
name: morning-routine
description: Execute complete morning workflow with daily note, task review, and planning.
allowed-tools: Read, Write, Edit, Glob
user-invocable: true
---
# Morning Routine Skill
Executes complete morning workflow. Executes complete morning workflow.
## Steps ## Steps
1. Create daily note 1. Create daily note
2. Review yesterday's uncomplete tasks 2. Review yesterday's incomplete tasks
3. Check calendar for today 3. Check calendar for today
4. Pull priority from weekly goals 4. Pull priority from weekly goals
5. Set time blocks 5. Set time blocks
@@ -413,9 +432,16 @@ Executes complete morning workflow.
### End-of-Day Automation ### End-of-Day Automation
Create `.claude/commands/evening.md`: Create `.claude/skills/evening-shutdown/SKILL.md`:
```markdown ```markdown
# Evening Shutdown ---
name: evening-shutdown
description: Complete end-of-day routine with task review, reflection, and git commit.
allowed-tools: Read, Write, Edit, Bash
user-invocable: true
---
# Evening Shutdown Skill
Complete end-of-day routine. Complete end-of-day routine.
@@ -430,9 +456,16 @@ Complete end-of-day routine.
### Project Kickoff Automation ### Project Kickoff Automation
Create `.claude/commands/kickoff.md`: Create `.claude/skills/project-kickoff/SKILL.md`:
```markdown ```markdown
# Project Kickoff ---
name: project-kickoff
description: Initialize new project with standard structure, CLAUDE.md, and planning docs.
allowed-tools: Write, Edit, Glob, Bash
user-invocable: true
---
# Project Kickoff Skill
Initialize new project with structure. Initialize new project with structure.
@@ -599,7 +632,7 @@ Use Tasker or Automate for:
- [ ] [Task from external system] - [ ] [Task from external system]
``` ```
## v2.0 Features: Hooks, Agents, Skills & Rules ## v2.1 Features: Unified Skills, Hooks, Agents & Rules
### Hooks (Automatic Behaviors) ### Hooks (Automatic Behaviors)
@@ -658,9 +691,9 @@ model: sonnet
- `goal-aligner` - Goal-activity alignment analysis - `goal-aligner` - Goal-activity alignment analysis
- `inbox-processor` - GTD-style inbox processing - `inbox-processor` - GTD-style inbox processing
### Skills (Auto-Discovered Capabilities) ### Skills (Unified with Slash Commands)
Skills are capabilities Claude discovers and uses automatically. Located in `.claude/skills/`: Skills and slash commands are now unified in Claude Code v2.1+. All skills are located in `.claude/skills/`:
#### Creating a Custom Skill #### Creating a Custom Skill
Create `.claude/skills/my-skill/SKILL.md`: Create `.claude/skills/my-skill/SKILL.md`:
@@ -669,6 +702,7 @@ Create `.claude/skills/my-skill/SKILL.md`:
name: my-skill name: my-skill
description: What this skill does. Use for [specific situations]. description: What this skill does. Use for [specific situations].
allowed-tools: Read, Write, Edit allowed-tools: Read, Write, Edit
user-invocable: true
--- ---
# Skill Instructions # Skill Instructions
@@ -677,9 +711,14 @@ allowed-tools: Read, Write, Edit
``` ```
#### Included Skills #### Included Skills
- `obsidian-vault-ops` - Vault file operations | Skill | Invocation | Purpose |
- `goal-tracking` - Goal cascade management |-------|------------|---------|
- `daily-workflow` - Daily routine structure | `daily` | `/daily` | Create daily notes, morning/midday/evening routines |
| `weekly` | `/weekly` | Run weekly review, reflect and plan |
| `push` | `/push` | Git commit and push |
| `onboard` | `/onboard` | Load vault context |
| `goal-tracking` | (auto) | Track goal progress |
| `obsidian-vault-ops` | (auto) | Vault file operations |
### Modular Rules ### Modular Rules

View File

@@ -126,18 +126,18 @@ claude init
claude "Hello, I'm setting up my PKM system" claude "Hello, I'm setting up my PKM system"
``` ```
### Step 2: Set Up Commands ### Step 2: Verify Skills
```bash ```bash
# The commands should already be in .claude/commands/ # Skills are in .claude/skills/ with each skill in its own directory
# Verify they exist: # Verify they exist:
ls .claude/commands/ ls .claude/skills/
# You should see: # You should see:
# daily.md weekly.md push.md onboard.md # daily/ weekly/ push/ onboard/ goal-tracking/ obsidian-vault-ops/
``` ```
### Step 3: Test Commands ### Step 3: Test Skills
```bash ```bash
# Load your context # Load your context
@@ -293,8 +293,8 @@ Run through this checklist to ensure everything is working:
- [ ] Obsidian opens your vault without errors - [ ] Obsidian opens your vault without errors
- [ ] CLAUDE.md has your personalized content - [ ] CLAUDE.md has your personalized content
- [ ] `/daily` command creates today's note - [ ] `/daily` skill creates today's note
- [ ] `/onboard` command loads your context - [ ] `/onboard` skill loads your context
- [ ] Git commits work locally - [ ] Git commits work locally
- [ ] GitHub remote is connected (if using) - [ ] GitHub remote is connected (if using)
- [ ] Goals files have your objectives - [ ] Goals files have your objectives
@@ -338,16 +338,16 @@ claude code /weekly
- Ensure path has no special characters - Ensure path has no special characters
- Try creating fresh vault and copying files - Try creating fresh vault and copying files
### Claude Commands Not Working ### Skills Not Working
```bash ```bash
# Verify Claude Code installation # Verify Claude Code installation
claude --version claude --version
# Check command files exist # Check skill directories exist
ls -la .claude/commands/ ls -la .claude/skills/
# Try running directly # Verify a skill file exists
claude code < .claude/commands/daily.md cat .claude/skills/daily/SKILL.md
``` ```
### Git Issues ### Git Issues

View File

@@ -87,4 +87,4 @@ When analyzing, surface these insights:
Works well with: Works well with:
- Weekly Reviewer agent for regular check-ins - Weekly Reviewer agent for regular check-ins
- Productivity Coach output style for accountability - Productivity Coach output style for accountability
- `/onboard` command for full context - `/onboard` skill for full context

View File

@@ -113,5 +113,5 @@ Confirm? (y/n/modify)
Works well with: Works well with:
- Note Organizer agent for vault maintenance - Note Organizer agent for vault maintenance
- `/daily` command for routing to today's note - `/daily` skill for routing to today's note
- Weekly review for processing backlog - Weekly review for processing backlog

View File

@@ -68,6 +68,6 @@ Wait for user confirmation before making changes.
## Integration ## Integration
Works well with: Works well with:
- `/onboard` command for initial context - `/onboard` skill for initial context
- Productivity Coach output style for guidance - Productivity Coach output style for guidance
- Weekly review workflow for regular maintenance - Weekly review workflow for regular maintenance

View File

@@ -82,6 +82,6 @@ When Productivity Coach output style is active, include probing questions:
## Integration ## Integration
Works well with: Works well with:
- `/weekly` command for structured workflow - `/weekly` skill for structured workflow
- Goal Aligner agent for deep analysis - Goal Aligner agent for deep analysis
- Note Organizer agent for archiving old notes - Note Organizer agent for archiving old notes

View File

@@ -1,115 +0,0 @@
# Daily Note Creator Command
Creates today's daily note from the template, or opens it if it already exists.
## Installation
Copy this file to `.claude/commands/daily.md` in your vault root.
## Usage
```
claude code /daily
```
## Configuration
Customize these paths to match your vault structure:
```javascript
// Path Configuration (customize these)
const DAILY_NOTES_FOLDER = "Daily Notes";
const TEMPLATE_PATH = "Templates/Daily Template.md";
const DATE_FORMAT = "YYYY-MM-DD"; // Change if you prefer different format
```
## What This Command Does
1. **Checks if today's note exists**
- If yes: Opens the existing note
- If no: Creates new note from template
2. **Template Processing**
- Replaces `{{date}}` with today's date
- Replaces `{{date:format}}` with formatted dates
- Handles date arithmetic (e.g., `{{date-1}}` for yesterday)
3. **Automatic Organization**
- Places note in correct folder
- Names file with today's date
- Preserves your template structure
## Template Variables
Your daily template can use these variables:
- `{{date}}` - Today's date in default format
- `{{date:dddd}}` - Day name (e.g., Monday)
- `{{date:MMMM DD, YYYY}}` - Formatted date
- `{{date-1:YYYY-MM-DD}}` - Yesterday's date
- `{{date+1:YYYY-MM-DD}}` - Tomorrow's date
- `{{time}}` - Current time
## Example Workflow
1. Morning routine:
```
claude code /daily
```
Creates today's note with your template
2. Review yesterday:
The template automatically links to yesterday's note
3. Plan tomorrow:
End of day, set tomorrow's priority in the reflection
## Customization Ideas
### Different Date Formats
Change `DATE_FORMAT` to:
- `"YYYY-MM-DD"` - Standard ISO format (recommended)
- `"MM-DD-YYYY"` - US format
- `"DD-MM-YYYY"` - European format
- `"YYYY-MM-DD-ddd"` - Include day abbreviation
### Folder Organization
Organize by month/year:
```javascript
const year = new Date().getFullYear();
const month = String(new Date().getMonth() + 1).padStart(2, '0');
const DAILY_NOTES_FOLDER = `Daily Notes/${year}/${month}`;
```
### Multiple Templates
For different day types:
```javascript
const dayOfWeek = new Date().getDay();
const TEMPLATE_PATH = dayOfWeek === 1
? "Templates/Monday Template.md" // Special Monday template
: "Templates/Daily Template.md"; // Regular template
```
## Troubleshooting
### Note not created?
- Check template path exists
- Verify folder permissions
- Ensure template file is readable
### Wrong date format?
- Adjust `DATE_FORMAT` constant
- Check system date settings
### Links not working?
- Verify date format matches
- Check file naming convention
## Related Commands
- `/weekly` - Create weekly review
- `/push` - Save changes to Git
- `/onboard` - Load context
---
*Command Version: 1.0*
*Compatible with: Claude Code CLI*
**Pro Tip:** Run this as part of your morning routine for consistency!

View File

@@ -1,302 +0,0 @@
# Onboard Command
Loads all CLAUDE.md files from your vault to provide comprehensive context to Claude Code for intelligent assistance.
## Installation
Copy this file to `.claude/commands/onboard.md` in your vault root.
## Usage
```
claude code /onboard
```
For specific project context:
```
claude code /onboard Projects/MyProject
```
## Configuration
Customize context loading:
```javascript
// Configuration
const CLAUDE_FILE_NAME = "CLAUDE.md";
const MAX_DEPTH = 5; // How deep to search for CLAUDE.md files
const INCLUDE_TEMPLATES = false; // Load template files too
const LOAD_RECENT_NOTES = true; // Include last 7 days of daily notes
```
## What This Command Does
1. **Discovers Context Files**
- Searches for all CLAUDE.md files
- Traverses project directories
- Respects depth limits
2. **Loads Hierarchical Context**
- Root CLAUDE.md first (global context)
- Project-specific CLAUDE.md files
- Recent daily notes for current state
3. **Builds Understanding**
- Your personal mission/goals
- Project structures and status
- Workflow preferences
- Custom conventions
## Context Hierarchy
```
vault/
├── CLAUDE.md # [1] Global context - loaded first
├── Projects/
│ ├── Project A/
│ │ └── CLAUDE.md # [2] Project context - loaded second
│ └── Project B/
│ └── CLAUDE.md # [3] Another project context
└── Areas/
└── Health/
└── CLAUDE.md # [4] Area-specific context
```
## CLAUDE.md File Structure
### Root CLAUDE.md Should Include
```markdown
# System Context for Claude
## Personal Mission
[Your life mission/purpose]
## Current Focus
[What you're working on now]
## Preferences
- Writing style: [Formal/Casual/Technical]
- Detail level: [High/Medium/Low]
- Decision making: [Collaborative/Directive]
## Conventions
- File naming: [Your patterns]
- Tag system: [Your tags]
- Workflow: [Your process]
```
### Project CLAUDE.md Should Include
```markdown
# Project: [Name]
## Overview
[What this project is about]
## Current Status
[Where things stand]
## Key Decisions
[Important choices made]
## Next Steps
[What needs to happen]
## Context for Claude
[Specific things Claude should know]
```
## Smart Context Loading
### Recent Activity
Automatically includes:
```javascript
// Last 7 days of daily notes
const recentNotes = getDailyNotes(7);
// Current week's review
const weeklyReview = getCurrentWeekReview();
// Active project updates
const activeProjects = getModifiedProjects(3); // days
```
### Selective Loading
For focused assistance:
```bash
# Load only specific project
claude code /onboard Projects/WebApp
# Load only certain areas
claude code /onboard Areas/Health
# Full context load
claude code /onboard all
```
## Use Cases
### Project Work
```bash
claude code /onboard Projects/MyApp
claude code "Help me refactor the authentication module"
```
### Daily Planning
```bash
claude code /onboard
claude code "Review my goals and suggest today's priorities"
```
### Weekly Review
```bash
claude code /onboard Goals
claude code "Analyze my week and suggest improvements"
```
## Context Variables
Your CLAUDE.md files can include variables:
```markdown
## Variables for Claude
- DEFAULT_LANGUAGE: JavaScript
- TIMEZONE: America/New_York
- WORK_HOURS: 9am-5pm
- PREFERRED_FRAMEWORKS: React, Node.js
- COMMUNICATION_STYLE: Direct and concise
```
Claude will use these for better assistance.
## Advanced Features
### Conditional Context
```markdown
## Context by Day
<!-- IF: Monday -->
Focus on weekly planning and goal setting
<!-- IF: Friday -->
Focus on review and closure
<!-- ENDIF -->
```
### Project Templates
```markdown
## When Creating New Projects
Use this structure:
1. Create project folder
2. Add CLAUDE.md
3. Set up initial files
4. Create project note from template
```
### Workflow Triggers
```markdown
## Automated Workflows
When I say "morning routine":
1. Create daily note
2. Review yesterday's tasks
3. Set today's priority
4. Check calendar
```
## Performance Optimization
### Large Vaults
For vaults with many files:
```javascript
// Limit context loading
const OPTIONS = {
maxFiles: 10,
maxSizePerFile: 50000, // characters
prioritize: ["Goals", "Active Projects"]
};
```
### Caching
Context is cached for session:
```javascript
// Cache duration
const CACHE_DURATION = 3600000; // 1 hour
// Force refresh
claude code /onboard --refresh
```
## Privacy & Security
### Sensitive Information
Never include in CLAUDE.md:
- Passwords or credentials
- Personal identification numbers
- Financial account details
- Private personal information
### Safe Context Examples
✅ "I work in healthcare technology"
✅ "My projects involve web development"
✅ "I prefer morning work sessions"
❌ "My SSN is..."
❌ "My bank account..."
❌ "My private API key..."
## Best Practices
### Keep Context Updated
- Review CLAUDE.md files monthly
- Update after major decisions
- Remove outdated information
- Add new learnings
### Be Specific
- Clear project descriptions
- Specific preferences
- Concrete examples
- Defined conventions
### Hierarchical Information
- Global → Area → Project → Task
- General → Specific
- Strategic → Tactical
## Troubleshooting
### Context Not Loading?
- Check file names (CLAUDE.md exactly)
- Verify file permissions
- Ensure valid markdown
- Check file encoding (UTF-8)
### Too Much Context?
- Use selective loading
- Reduce MAX_DEPTH
- Archive old projects
- Clean up CLAUDE.md files
### Conflicting Instructions?
- More specific overrides general
- Project overrides global
- Recent overrides old
## Integration Examples
### With Daily Command
```bash
claude code /onboard
claude code /daily
# Claude now knows your full context for the daily note
```
### With Push Command
```bash
claude code /onboard
# Make changes with Claude's help
claude code /push "Changes guided by Claude"
```
## Related Commands
- `/daily` - Create daily note
- `/weekly` - Run weekly review
- `/push` - Save to Git
---
*Command Version: 1.0*
*Optimized for: Quick context loading*
**Remember:** Good context leads to better assistance. Keep your CLAUDE.md files current!

View File

@@ -1,261 +0,0 @@
# Git Push Command
Automates the Git workflow to save your notes with a meaningful commit message and push to remote repository.
## Installation
Copy this file to `.claude/commands/push.md` in your vault root.
## Usage
```
claude code /push
```
Or with a custom message:
```
claude code /push "Completed project planning"
```
## Configuration
Customize these settings:
```javascript
// Configuration
const DEFAULT_REMOTE = "origin";
const DEFAULT_BRANCH = "main";
const AUTO_PULL_FIRST = true; // Pull before pushing to avoid conflicts
const INCLUDE_TIMESTAMP = true; // Add timestamp to commit message
```
## What This Command Does
1. **Stages All Changes**
- Adds all modified files
- Includes new files
- Removes deleted files
2. **Creates Smart Commit Message**
- Uses provided message, or
- Auto-generates from changes
- Includes date/time stamp
- Summarizes key modifications
3. **Syncs with Remote**
- Pulls latest changes (if enabled)
- Pushes to remote repository
- Handles merge conflicts gracefully
## Commit Message Format
### Automatic Messages
Based on your changes:
```
Daily note for 2024-01-15 + 3 project updates
- Added: Daily Notes/2024-01-15.md
- Modified: Projects/Learning Spanish/notes.md
- Modified: Goals/2. Monthly Goals.md
```
### With Timestamp
```
[2024-01-15 09:30] Completed weekly review
```
### Manual Message
```
claude code /push "Major project milestone reached"
```
## Smart Features
### Conflict Prevention
```javascript
// Always pull before push
if (AUTO_PULL_FIRST) {
git pull --rebase origin main
}
```
### Change Summary
Analyzes your changes:
- Daily notes added
- Projects modified
- Goals updated
- Templates changed
### Safety Checks
- Verifies Git repository exists
- Checks for uncommitted changes
- Ensures remote is configured
- Validates branch exists
## Workflow Integration
### Morning Routine
```bash
claude code /daily # Create daily note
# ... work on notes ...
claude code /push "Morning planning complete"
```
### End of Day
```bash
# Complete daily reflection
claude code /push # Auto-message with summary
```
### After Weekly Review
```bash
claude code /weekly # Run weekly review
claude code /push "Weekly review - Week 3"
```
## Advanced Options
### Multiple Remotes
```javascript
// Push to multiple remotes
const REMOTES = ["origin", "backup"];
REMOTES.forEach(remote => {
git push remote main
});
```
### Branch-Based Workflow
```javascript
// Create feature branches for projects
const project = "new-feature";
git checkout -b project
git add .
git commit -m message
git push -u origin project
```
### Automated Backups
```javascript
// Schedule automatic pushes
const BACKUP_INTERVAL = 3600000; // 1 hour
setInterval(() => {
git add .
git commit -m "Automated backup"
git push
}, BACKUP_INTERVAL);
```
## Git Configuration
### Initial Setup
```bash
# Initialize repository
git init
# Add remote
git remote add origin https://github.com/username/vault.git
# Set user info
git config user.name "Your Name"
git config user.email "your.email@example.com"
```
### Recommended .gitignore
```
.obsidian/workspace*
.obsidian/cache
.trash/
.DS_Store
```
## Commit Message Best Practices
### Good Messages
- ✅ "Completed Q1 planning and project kickoff"
- ✅ "Daily note: Fixed bug in authentication"
- ✅ "Weekly review - adjusted monthly goals"
### Avoid
- ❌ "Updates"
- ❌ "Changes"
- ❌ "WIP"
## Handling Conflicts
If conflicts occur:
1. **Auto-resolve attempts**
- Favors local changes for notes
- Merges both versions when possible
2. **Manual resolution needed**
- Opens conflict markers
- Prompts for resolution
- Guides through process
## Mobile Sync via GitHub
This enables:
- View notes on GitHub mobile app
- Create issues for tasks
- Review changes on any device
- Emergency access from any browser
## Security Considerations
### Private Repository
Always use private repos for personal notes:
```bash
# GitHub CLI
gh repo create vault --private
# Or via settings
# Repository Settings > Make Private
```
### Sensitive Information
Never commit:
- Passwords
- API keys
- Personal identification
- Financial information
Use `.gitignore` for sensitive files:
```
private/
credentials.md
.env
```
## Troubleshooting
### Push Rejected?
```bash
# Pull first
git pull --rebase origin main
# Then push again
git push origin main
```
### Not a Git Repository?
```bash
# Initialize
git init
# Add remote
git remote add origin [URL]
```
### Large Files Issue?
```bash
# Use Git LFS for images/attachments
git lfs track "*.png"
git lfs track "*.pdf"
```
## Related Commands
- `/daily` - Create daily note
- `/weekly` - Run weekly review
- `/onboard` - Load context
---
*Command Version: 1.0*
*Requires: Git installed and configured*
**Pro Tip:** Commit early and often - your future self will thank you!

View File

@@ -1,201 +0,0 @@
# Weekly Review Command
Facilitates your weekly review process by creating a new review note and helping you reflect on the past week while planning the next.
## Installation
Copy this file to `.claude/commands/weekly.md` in your vault root.
## Usage
```
claude code /weekly
```
## Configuration
Customize these settings for your workflow:
```javascript
// Configuration (customize these)
const WEEKLY_FOLDER = "Goals";
const WEEKLY_TEMPLATE = "Templates/Weekly Review Template.md";
const REVIEW_DAY = 0; // 0=Sunday, 1=Monday, etc.
const TIME_INVESTMENT_TARGET = 30; // minutes for review
```
## What This Command Does
1. **Creates Weekly Review Note**
- Uses weekly review template
- Names it with current week's date
- Places in Goals folder
2. **Guides Review Process**
- Reviews last week's accomplishments
- Identifies incomplete tasks
- Plans upcoming week
- Aligns with monthly goals
3. **Automates Housekeeping**
- Archives old daily notes
- Updates project statuses
- Cleans up completed tasks
## Review Process Steps
### Step 1: Reflection (10 minutes)
- Review daily notes from past week
- Identify wins and challenges
- Capture lessons learned
### Step 2: Goal Alignment (10 minutes)
- Check monthly goal progress
- Adjust weekly priorities
- Ensure alignment with yearly goals
### Step 3: Planning (10 minutes)
- Set ONE big thing for the week
- Schedule important tasks
- Block time for deep work
## Interactive Prompts
The command will guide you through:
1. **"What were your top 3 wins this week?"**
- Celebrates progress
- Builds momentum
- Documents achievements
2. **"What were your main challenges?"**
- Identifies obstacles
- Plans solutions
- Learns from difficulties
3. **"What's your ONE big thing next week?"**
- Forces prioritization
- Creates focus
- Drives meaningful progress
## Weekly Review Checklist
The command helps you:
- [ ] Review all daily notes
- [ ] Process inbox items
- [ ] Update project statuses
- [ ] Check upcoming calendar
- [ ] Review monthly goals
- [ ] Plan next week's priorities
- [ ] Block time for important work
- [ ] Clean digital workspace
- [ ] Archive completed items
- [ ] Commit changes to Git
## Automation Features
### Auto-Archive
Moves daily notes older than 30 days to Archives:
```javascript
const ARCHIVE_AFTER_DAYS = 30;
// Automatically moves old notes to Archives/YYYY/MM/
```
### Project Status Update
Prompts for each active project:
```javascript
// For each project folder:
// - Update completion percentage
// - Note blockers
// - Set next actions
```
### Habit Tracking
Calculates habit success rates:
```javascript
// Counts habit checkboxes from daily notes
// Shows completion percentage
// Identifies patterns
```
## Customization Options
### Different Review Days
```javascript
// For Monday reviews:
const REVIEW_DAY = 1;
// For Friday reviews:
const REVIEW_DAY = 5;
```
### Monthly Reviews
Add monthly review trigger:
```javascript
const today = new Date();
const lastDayOfMonth = new Date(today.getFullYear(), today.getMonth() + 1, 0).getDate();
if (today.getDate() === lastDayOfMonth) {
// Trigger monthly review too
}
```
### Sprint-Based Reviews
For agile workflows:
```javascript
const SPRINT_LENGTH = 14; // days
const SPRINT_START = new Date('2024-01-01');
// Calculate sprint number and adjust review
```
## Integration with Goals
The command automatically:
- Links to [[2. Monthly Goals]]
- Updates [[1. Yearly Goals]] progress
- Creates new week entry in review log
## Best Practices
### Consistent Timing
- Same day each week
- Same time if possible
- Block calendar time
- Treat as non-negotiable
### Preparation
- Clean inbox before review
- Have calendar ready
- Gather project updates
- Review any feedback
### Follow-through
- Share highlights with team/family
- Update external systems
- Communicate changes
- Celebrate wins
## Troubleshooting
### Review not created?
- Check template exists
- Verify folder structure
- Ensure write permissions
### Links broken?
- Verify file naming
- Check date formats
- Update link syntax
### Too time-consuming?
- Use timer for each section
- Prepare throughout week
- Simplify template
## Related Commands
- `/daily` - Create daily note
- `/push` - Commit to Git
- `/onboard` - Load all context
---
*Command Version: 1.0*
*Optimal Time: Sunday evening or Monday morning*
**Remember:** The best review is the one you actually do. Keep it simple and consistent!

View File

@@ -1,12 +1,53 @@
--- ---
name: daily-workflow name: daily
description: Morning routine, midday check-in, and evening shutdown workflows. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines. description: Create daily notes and manage morning, midday, and evening routines. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines or when asked to create today's note.
allowed-tools: Read, Write, Edit, Glob, Grep allowed-tools: Read, Write, Edit, Glob, Grep
user-invocable: true
--- ---
# Daily Workflow Skill # Daily Workflow Skill
Structured workflows for morning planning, midday check-ins, and evening shutdowns. Creates daily notes and provides structured workflows for morning planning, midday check-ins, and evening shutdowns.
## Usage
Invoke with `/daily` or ask Claude to create today's note or help with daily routines.
### Create Today's Note
```
/daily
```
Or simply ask:
- "Create today's daily note"
- "Start my morning routine"
- "Help me with evening shutdown"
## Daily Note Creation
### What Happens
1. **Checks if today's note exists**
- If yes: Opens the existing note
- If no: Creates new note from template
2. **Template Processing**
- Replaces `{{date}}` with today's date
- Replaces `{{date:format}}` with formatted dates
- Handles date arithmetic (e.g., `{{date-1}}` for yesterday)
3. **Automatic Organization**
- Places note in `Daily Notes/` folder
- Names file with today's date (YYYY-MM-DD.md)
- Preserves template structure
### Template Variables
Your daily template can use:
- `{{date}}` - Today's date in default format
- `{{date:dddd}}` - Day name (e.g., Monday)
- `{{date:MMMM DD, YYYY}}` - Formatted date
- `{{date-1:YYYY-MM-DD}}` - Yesterday's date
- `{{date+1:YYYY-MM-DD}}` - Tomorrow's date
- `{{time}}` - Current time
## Morning Routine (5-10 minutes) ## Morning Routine (5-10 minutes)
@@ -72,9 +113,9 @@ Structured workflows for morning planning, midday check-ins, and evening shutdow
- [ ] Tomorrow's priority identified - [ ] Tomorrow's priority identified
- [ ] Changes committed - [ ] Changes committed
## Daily Note Sections ## Daily Note Structure
Standard daily note structure: Standard daily note template:
```markdown ```markdown
# {{date}} # {{date}}
@@ -83,9 +124,9 @@ Standard daily note structure:
> What's the ONE thing that would make today successful? > What's the ONE thing that would make today successful?
## Time Blocks ## Time Blocks
- 🌅 Morning (9-12): - Morning (9-12):
- ☀️ Afternoon (12-5): - Afternoon (12-5):
- 🌙 Evening (5+): - Evening (5+):
## Tasks ## Tasks
### Must Do Today ### Must Do Today
@@ -121,10 +162,30 @@ Standard daily note structure:
- Minimize context switching - Minimize context switching
- Protect deep work blocks - Protect deep work blocks
## Configuration
Customize paths to match your vault:
- Daily notes folder: `Daily Notes/`
- Template location: `Templates/Daily Template.md`
- Date format: `YYYY-MM-DD`
### Different Date Formats
- `YYYY-MM-DD` - Standard ISO format (recommended)
- `MM-DD-YYYY` - US format
- `DD-MM-YYYY` - European format
- `YYYY-MM-DD-ddd` - Include day abbreviation
### Folder Organization by Month
Organize daily notes by month/year:
```
Daily Notes/2024/01/2024-01-15.md
```
## Integration ## Integration
Works with: Works with:
- `/daily` command for note creation - `/push` - Commit end-of-day changes
- `/push` command for end-of-day commit - `/weekly` - Weekly planning uses daily notes
- Productivity Coach for accountability - `/onboard` - Load context before planning
- Goal Tracking skill for alignment - Goal tracking skill - Align daily tasks to goals
- Productivity Coach - Accountability for daily routines

View File

@@ -0,0 +1,181 @@
---
name: onboard
description: Load CLAUDE.md context files from vault for comprehensive understanding. Discovers hierarchical context, recent notes, and project states. Use at start of session or when Claude needs full vault context.
allowed-tools: Read, Glob, Grep
user-invocable: true
---
# Onboard Skill
Loads all CLAUDE.md files from your vault to provide comprehensive context for intelligent assistance.
## Usage
Invoke with `/onboard` or ask Claude to learn about your vault.
### Full Context Load
```
/onboard
```
### Specific Project Context
```
/onboard Projects/MyProject
```
## What This Skill Does
1. **Discovers Context Files**
- Searches for all CLAUDE.md files
- Traverses project directories
- Respects depth limits
2. **Loads Hierarchical Context**
- Root CLAUDE.md first (global context)
- Project-specific CLAUDE.md files
- Recent daily notes for current state
3. **Builds Understanding**
- Your personal mission/goals
- Project structures and status
- Workflow preferences
- Custom conventions
## Context Hierarchy
```
vault/
├── CLAUDE.md # [1] Global context - loaded first
├── Projects/
│ ├── Project A/
│ │ └── CLAUDE.md # [2] Project context
│ └── Project B/
│ └── CLAUDE.md # [3] Another project context
└── Areas/
└── Health/
└── CLAUDE.md # [4] Area-specific context
```
## CLAUDE.md File Structure
### Root CLAUDE.md Should Include
```markdown
# System Context for Claude
## Personal Mission
[Your life mission/purpose]
## Current Focus
[What you're working on now]
## Preferences
- Writing style: [Formal/Casual/Technical]
- Detail level: [High/Medium/Low]
## Conventions
- File naming: [Your patterns]
- Tag system: [Your tags]
```
### Project CLAUDE.md Should Include
```markdown
# Project: [Name]
## Overview
[What this project is about]
## Current Status
[Where things stand]
## Key Decisions
[Important choices made]
## Next Steps
[What needs to happen]
```
## Smart Context Loading
### Recent Activity
Automatically considers:
- Last 7 days of daily notes
- Current week's review
- Recently modified projects
### Selective Loading
For focused assistance:
```
/onboard Projects/WebApp # Only specific project
/onboard Goals # Only goals context
```
## Use Cases
### Starting a Session
```
/onboard
"Help me plan my day based on my goals"
```
### Project Work
```
/onboard Projects/MyApp
"Help me refactor the authentication module"
```
### Weekly Planning
```
/onboard Goals
"Analyze my week and suggest improvements"
```
## Context Variables
Your CLAUDE.md files can include preferences:
```markdown
## Variables for Claude
- DEFAULT_LANGUAGE: JavaScript
- TIMEZONE: America/New_York
- COMMUNICATION_STYLE: Direct and concise
```
## Best Practices
### Keep Context Updated
- Review CLAUDE.md files monthly
- Update after major decisions
- Remove outdated information
- Add new learnings
### Be Specific
- Clear project descriptions
- Specific preferences
- Concrete examples
- Defined conventions
### Hierarchical Information
- Global → Area → Project → Task
- General → Specific
- Strategic → Tactical
## Privacy & Security
### Never Include in CLAUDE.md
- Passwords or credentials
- Personal identification numbers
- Financial account details
- Private API keys
### Safe Context Examples
- "I work in healthcare technology"
- "My projects involve web development"
- "I prefer morning work sessions"
## Integration
Works with:
- All other skills (provides context)
- `/daily` - Better daily planning with context
- `/weekly` - Informed weekly reviews
- Goal tracking - Understand goal cascade

View File

@@ -0,0 +1,145 @@
---
name: push
description: Commit and push vault changes to Git with smart commit messages. Auto-stages files, creates meaningful commits, and syncs with remote. Use after making vault changes or at end of day.
allowed-tools: Bash, Read, Glob
user-invocable: true
---
# Git Push Skill
Automates Git workflow to save your notes with meaningful commit messages and push to remote repository.
## Usage
Invoke with `/push` or ask Claude to save/commit your changes.
### Basic Usage
```
/push
```
### With Custom Message
```
/push "Completed project planning"
```
## What This Skill Does
1. **Stages All Changes**
- Adds all modified files
- Includes new files
- Removes deleted files
2. **Creates Smart Commit Message**
- Uses provided message, or
- Auto-generates from changes
- Includes date/time stamp
- Summarizes key modifications
3. **Syncs with Remote**
- Pulls latest changes (if enabled)
- Pushes to remote repository
- Handles merge conflicts gracefully
## Commit Message Format
### Automatic Messages
Based on your changes:
```
Daily note for 2024-01-15 + 3 project updates
- Added: Daily Notes/2024-01-15.md
- Modified: Projects/Learning Spanish/notes.md
- Modified: Goals/2. Monthly Goals.md
```
### With Timestamp
```
[2024-01-15 09:30] Completed weekly review
```
## Workflow Integration
### Morning Routine
```
/daily # Create daily note
# ... work on notes ...
/push "Morning planning complete"
```
### End of Day
```
# Complete daily reflection
/push # Auto-message with summary
```
### After Weekly Review
```
/weekly # Run weekly review
/push "Weekly review - Week 3"
```
## Git Operations
### Standard Flow
1. `git add .` - Stage all changes
2. `git commit -m "message"` - Create commit
3. `git pull --rebase origin main` - Get remote changes
4. `git push origin main` - Push to remote
### Safety Checks
- Verify Git repository exists
- Check for uncommitted changes
- Ensure remote is configured
- Validate branch exists
## Conflict Handling
If conflicts occur:
1. Auto-resolve attempts (favor local for notes)
2. If manual resolution needed, guide through process
3. Never force push without explicit request
## Security Considerations
### Never Commit
- Passwords or credentials
- API keys
- Personal identification
- Financial information
### Use .gitignore for
```
private/
credentials.md
.env
.obsidian/workspace*
.obsidian/cache
.trash/
.DS_Store
```
## Troubleshooting
### Push Rejected?
Pull first, then push again:
```bash
git pull --rebase origin main
git push origin main
```
### Not a Git Repository?
```bash
git init
git remote add origin [URL]
```
### Large Files Issue?
Consider Git LFS for images/attachments.
## Integration
Works with:
- `/daily` - Commit after creating daily note
- `/weekly` - Commit after weekly review
- `/onboard` - No git needed for context loading
- Auto-commit hook for automatic saves

View File

@@ -0,0 +1,173 @@
---
name: weekly
description: Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
allowed-tools: Read, Write, Edit, Glob, Grep
user-invocable: true
---
# Weekly Review Skill
Facilitates your weekly review process by creating a review note and guiding reflection on the past week while planning the next.
## Usage
Invoke with `/weekly` or ask Claude to help with your weekly review.
```
/weekly
```
## What This Skill Does
1. **Creates Weekly Review Note**
- Uses weekly review template
- Names it with current week's date
- Places in Goals folder
2. **Guides Review Process**
- Reviews last week's accomplishments
- Identifies incomplete tasks
- Plans upcoming week
- Aligns with monthly goals
3. **Automates Housekeeping**
- Archives old daily notes
- Updates project statuses
- Cleans up completed tasks
## Review Process Steps
### Step 1: Reflection (10 minutes)
- Review daily notes from past week
- Identify wins and challenges
- Capture lessons learned
### Step 2: Goal Alignment (10 minutes)
- Check monthly goal progress
- Adjust weekly priorities
- Ensure alignment with yearly goals
### Step 3: Planning (10 minutes)
- Set ONE big thing for the week
- Schedule important tasks
- Block time for deep work
## Interactive Prompts
The skill guides you through:
1. **"What were your top 3 wins this week?"**
- Celebrates progress
- Builds momentum
- Documents achievements
2. **"What were your main challenges?"**
- Identifies obstacles
- Plans solutions
- Learns from difficulties
3. **"What's your ONE big thing next week?"**
- Forces prioritization
- Creates focus
- Drives meaningful progress
## Weekly Review Checklist
- [ ] Review all daily notes
- [ ] Process inbox items
- [ ] Update project statuses
- [ ] Check upcoming calendar
- [ ] Review monthly goals
- [ ] Plan next week's priorities
- [ ] Block time for important work
- [ ] Clean digital workspace
- [ ] Archive completed items
- [ ] Commit changes to Git
## Weekly Review Note Format
```markdown
# Weekly Review: YYYY-MM-DD
## Last Week's Wins
1.
2.
3.
## Challenges & Lessons
- Challenge:
- Lesson:
## Goal Progress
### Monthly Goals
- [ ] Goal 1 (XX%)
- [ ] Goal 2 (XX%)
### This Week's Contribution
- [Task] -> [[Goal]]
## Next Week Planning
### ONE Big Thing
>
### Key Tasks
- [ ]
- [ ]
- [ ]
### Time Blocks
- Monday:
- Tuesday:
- Wednesday:
- Thursday:
- Friday:
## Notes
```
## Automation Features
### Auto-Archive
Suggest moving daily notes older than 30 days to Archives.
### Project Status Update
For each active project:
- Update completion percentage
- Note blockers
- Set next actions
### Habit Tracking
Calculate habit success rates from daily notes:
- Count habit checkboxes
- Show completion percentage
- Identify patterns
## Best Practices
### Consistent Timing
- Same day each week (Sunday recommended)
- Same time if possible
- Block calendar time
- Treat as non-negotiable
### Preparation
- Clean inbox before review
- Have calendar ready
- Gather project updates
- Review any feedback
### Follow-through
- Share highlights with team/family
- Update external systems
- Communicate changes
- Celebrate wins
## Integration
Works with:
- `/daily` - Reviews daily notes from the week
- `/push` - Commit after completing review
- `/onboard` - Load context for informed review
- Goal tracking skill - Progress calculations
- `/daily` skill - Plan next week's routines

View File

@@ -26,14 +26,18 @@ See @Goals/2. Monthly Goals.md for this month's priorities.
**Status:** `#active`, `#waiting`, `#completed`, `#archived` **Status:** `#active`, `#waiting`, `#completed`, `#archived`
**Context:** `#work`, `#personal`, `#health`, `#learning`, `#family` **Context:** `#work`, `#personal`, `#health`, `#learning`, `#family`
## Available Commands ## Available Skills
| Command | Purpose | Skills are invoked with `/skill-name` or automatically by Claude when relevant.
|---------|---------|
| `/daily` | Create today's daily note from template | | Skill | Invocation | Purpose |
| `/weekly` | Run weekly review process | |-------|------------|---------|
| `/push` | Commit and push changes to Git | | `daily` | `/daily` | Create daily notes, morning/midday/evening routines |
| `/onboard` | Load full vault context | | `weekly` | `/weekly` | Run weekly review, reflect and plan |
| `push` | `/push` | Commit and push changes to Git |
| `onboard` | `/onboard` | Load full vault context |
| `goal-tracking` | (auto) | Track progress across goal cascade |
| `obsidian-vault-ops` | (auto) | Read/write vault files, manage wiki-links |
## Available Agents ## Available Agents
@@ -44,12 +48,6 @@ See @Goals/2. Monthly Goals.md for this month's priorities.
| `goal-aligner` | Check daily/weekly alignment with long-term goals | | `goal-aligner` | Check daily/weekly alignment with long-term goals |
| `inbox-processor` | GTD-style inbox processing | | `inbox-processor` | GTD-style inbox processing |
## Available Skills
- **obsidian-vault-ops** - Read/write vault files, manage wiki-links
- **goal-tracking** - Track progress across goal cascade
- **daily-workflow** - Morning/midday/evening routines
## Output Styles ## Output Styles
**Productivity Coach** (`/output-style coach`) **Productivity Coach** (`/output-style coach`)
@@ -92,5 +90,5 @@ See `CLAUDE.local.md.template` for format.
--- ---
*See @.claude/rules/ for detailed conventions* *See @.claude/rules/ for detailed conventions*
*Last Updated: 2024-12-19* *Last Updated: 2026-01-10*
*System Version: 2.0* *System Version: 2.1 (Unified Skills)*