.claude: move changelog writing into skill

Author: jamiebrynes7

.claude/skills/write-changelog/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: write-changelog
+description: Write or update changelog entries with user-focused language
+---
+
+# Changelog
+
+Write or update changelog entries following these guidelines:
+
+## Guidelines
+
+- **Focus on user benefits** rather than implementation details
+- **Keep entries concise** - typically a single line without subpoints
+- **Emphasize what the user can now do** or how their experience improves
+- **Avoid technical specifics** like state management, CSS classes, or internal architecture
+
+## Categories
+
+Entries are organized under these category headings:
+
+- `### ✨ Features` - New functionality for users
+- `### 🐛 Bug Fixes` - Corrections to existing behavior
+- `### 🔁 Changes` - Modifications to existing features
+- `### ⚙ Internal` - Technical changes (use sparingly, still user-focused)
+- `### 🌐 Translations` - New or updated translations
+- `### Breaking changes` - For major releases only
+- `### Deprecated` - Features being phased out
+
+## Unreleased Section
+
+Always add new entries to the `## Unreleased` section at the top of the changelog. Create the appropriate category heading if it doesn't exist yet. Entries are moved to a versioned section during the release process.
+
+## Examples
+
+Good:
+
+- "Added keyboard shortcuts for common actions"
+- "Tasks now sync automatically when Obsidian starts"
+- "Fixed tasks not appearing after editing"
+
+Bad:
+
+- "Refactored TaskStore to use Redux pattern with selectors"
+- "Added `useEffect` hook to trigger sync on mount"
+- "Fixed CSS specificity issue in task-list component"
+
+## Location
+
+The changelog is located at `docs/docs/changelog.md`.

docs/CLAUDE.md

@@ -11,53 +11,62 @@ This is the documentation site for the Sync with Todoist Plugin for Obsidian. Th
 All commands should be run from this `docs/` directory:
 
 ### Development
+
 - `npm start` - Start local development server (usually runs on http://localhost:3000)
 - `npm run build` - Build documentation site for production
 - `npm run serve` - Serve built site locally
 - `npm run clear` - Clear Docusaurus cache
 
 ### Documentation Management
+
 - `npm run bump-version -- ${VERSION}` - Create new versioned documentation (e.g., `npm run bump-version -- 2.2.0`)
 - `npm run write-translations` - Extract translatable strings
 - `npm run write-heading-ids` - Add heading IDs to markdown files
 
 ### Quality
+
 - `npm run typecheck` - Run TypeScript type checking
 
 ## Documentation Structure
 
 ### Core Documentation (`docs/`)
+
 - `overview.md` - Main plugin introduction and features
 - `setup.md` - Installation and initial configuration
 - `configuration.md` - Detailed plugin settings
 - `query-blocks.md` - Query language documentation
 - `changelog.md` - Version history and changes
 
 ### Commands Documentation (`docs/commands/`)
+
 - `add-task.md` - Creating tasks from Obsidian
 - `sync-with-todoist.md` - Manual sync functionality
 
 ### Contributing Documentation (`docs/contributing/`)
+
 - `general.md` - Development setup and workflow
 - `release-process.md` - How to release new versions
 - `translation.mdx` - Translation contribution guide
 
 ## Versioned Documentation
 
 The site supports versioned documentation with past versions stored in:
+
 - `versioned_docs/version-X.Y.Z/` - Snapshot of docs for each version
 - `versioned_sidebars/` - Sidebar configuration for each version
 - `versions.json` - List of available versions
 
 ## Site Configuration
 
 ### Docusaurus Config (`docusaurus.config.ts`)
+
 - Site metadata and URL configuration
 - GitHub Pages deployment settings
 - Theme and navigation configuration
 - Versioning setup
 
 ### Customization
+
 - `src/css/custom.css` - Site-wide styling overrides
 - `src/components/` - Custom React components
 - `src/pages/` - Custom pages (like the homepage)
@@ -66,22 +75,19 @@ The site supports versioned documentation with past versions stored in:
 ## Development Notes
 
 ### Adding New Documentation
+
 1. Create markdown files in the `docs/` directory
 2. Update `sidebars.ts` to include new pages in navigation
 3. Use MDX format for pages requiring React components
 
-### Changelog Guidelines
-- Focus on user benefits rather than implementation details
-- Keep feature entries concise - typically a single line without subpoints
-- Emphasize what the user can now do or how their experience improves
-- Avoid technical specifics like state management, CSS classes, or internal architecture
-
 ### Managing Versions
+
 - Only cut new documentation versions for minor/major releases
 - Patch releases typically don't need new doc versions
 - Version bumping copies current docs to versioned storage
 
 ### Translation Support
+
 - Site is configured for internationalization but currently English-only
 - Translation status tracking in `translation-status.json`
-- Custom `TranslationStatus` component for displaying translation progress
+- Custom `TranslationStatus` component for displaying translation progress