fix: resolve lonely if ESLint warning

This commit is contained in:
Noah Brier
2025-09-15 08:49:07 -04:00
parent 61d14875d5
commit 3909ab476c
29 changed files with 1300 additions and 790 deletions
+33 -13
View File
@@ -1,18 +1,22 @@
---
description: Add or update YAML frontmatter properties to enhance note organization
description:
Add or update YAML frontmatter properties to enhance note organization
argument-hint: [file or folder path]
allowed-tools: Read, Write, Edit, Glob
---
You will analyze Obsidian notes and add intelligent YAML frontmatter properties to enhance organization and discoverability.
You will analyze Obsidian notes and add intelligent YAML frontmatter properties
to enhance organization and discoverability.
## Input
- Path: ${1} (file or folder to process)
- Current date: !`date +%Y-%m-%d`
## Your Task
### Step 1: Identify Notes to Process
```bash
# If single file
Read the specified file
@@ -24,6 +28,7 @@ Find all .md files in folder
### Step 2: Analyze Note Content
For each note, examine:
- Main topics and themes
- Note type (meeting, daily, reference, project)
- Key entities (people, projects, dates)
@@ -35,22 +40,24 @@ For each note, examine:
#### Standard Properties by Note Type
**Meeting Notes:**
```yaml
---
title: [Descriptive meeting title]
date: YYYY-MM-DD
type: meeting
attendees: ["Person 1", "Person 2"]
attendees: ['Person 1', 'Person 2']
project: Project Name
tags: [meeting, project-name]
action_items:
- "Action item 1"
- "Action item 2"
action_items:
- 'Action item 1'
- 'Action item 2'
status: complete
---
```
**Daily Notes:**
```yaml
---
title: Daily Note - YYYY-MM-DD
@@ -58,12 +65,13 @@ date: YYYY-MM-DD
type: daily-note
tags: [daily]
highlights:
- "Key event or thought"
- 'Key event or thought'
mood: productive
---
```
**Reference/Article Notes:**
```yaml
---
title: [Article or concept title]
@@ -77,13 +85,14 @@ key_concepts: [concept1, concept2]
```
**Project Notes:**
```yaml
---
title: [Project Name - Component]
type: project
status: in-progress
deadline: YYYY-MM-DD
stakeholders: ["Person 1", "Team 2"]
stakeholders: ['Person 1', 'Team 2']
tags: [project, area]
priority: high
---
@@ -92,6 +101,7 @@ priority: high
### Step 4: Apply Properties
For each note:
1. Check for existing frontmatter
2. Merge new properties (don't duplicate)
3. Fix any deprecated formats:
@@ -106,22 +116,23 @@ For each note:
# Format:
---
property: value
list_property: ["item1", "item2"]
list_property: ['item1', 'item2']
date_property: YYYY-MM-DD
linked_property: "[[Note Name]]"
linked_property: '[[Note Name]]'
---
[Original content]
```
## Property Guidelines
### Naming Conventions
- Use lowercase with underscores: `date_created`, `action_items`
- Be consistent with existing vault patterns
- Prefer clear over clever names
### Value Types
- **Text**: Simple strings, use quotes for links
- **List**: Arrays for multiple values
- **Date**: ISO format (YYYY-MM-DD)
@@ -129,6 +140,7 @@ linked_property: "[[Note Name]]"
- **Checkbox**: For boolean states
### Quality Checks
- ✅ Valid YAML syntax
- ✅ No duplicate properties
- ✅ Appropriate property types
@@ -138,18 +150,23 @@ linked_property: "[[Note Name]]"
## Special Cases
### Untitled Notes
Generate title from:
1. First heading if exists
2. First paragraph summary
3. Main topic/concept discussed
### Bulk Processing
When processing folders:
- Maintain consistency across similar notes
- Use same property names for same concepts
- Report summary of changes made
### Existing Properties
- Preserve valid existing properties
- Update deprecated formats
- Merge new properties carefully
@@ -158,17 +175,19 @@ When processing folders:
## Examples
### Before:
```markdown
Had a great meeting with the team about Q1 planning...
```
### After:
```markdown
---
title: Q1 Planning Team Meeting
date: 2025-09-02
type: meeting
attendees: ["Team"]
attendees: ['Team']
project: Q1 Planning
tags: [meeting, planning, q1-2025]
status: complete
@@ -177,4 +196,5 @@ status: complete
Had a great meeting with the team about Q1 planning...
```
Remember: Properties should enhance organization, not clutter. Only add what provides value for finding and connecting notes.
Remember: Properties should enhance organization, not clutter. Only add what
provides value for finding and connecting notes.