kalinichenko88

Run the daily AI tech news digest pipeline — collect, deduplicate, summarize, deliver

Create a new release — bump version, tag, generate changelog, create GitHub Release

Add a new news source (RSS or GitHub release) to ai-digest config

Validate sources.yml structure and check that all URLs/endpoints are reachable. Use when the user wants to check, verify, validate, or test the sources config, or after adding/modifying sources. Also use when the user mentions broken links, 404 errors, or source health checks.

Cut and publish a new release of the Budget Planner Obsidian plugin. Use this WHENEVER the user wants to release, publish, ship a new version, bump the version, cut a tag, or add a CHANGELOG entry — even a bare "release" or "let's ship 1.3.0". Drives the whole local side: derive the next semver from the commits, draft the CHANGELOG section, bump the version files, run the full verification gate, commit, and (only after explicit confirmation) tag and push — the tag push triggers the GitHub Actions release workflow. Then watch CI and report the published release.

Comprehensive guidelines for Obsidian.md plugin development including all 27 ESLint rules, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, and submission requirements. Use when working with Obsidian plugins, main.ts files, manifest.json, Plugin class, MarkdownView, TFile, vault operations, or any Obsidian API development.

Use when adding or changing any page, section, or UI component in this repo (kalinichenko.dev), or when asked to verify design-system / DESIGN.md compliance, contrast, or visual consistency.

Cut and publish a new npm release of telegram-agent-kit. Use this WHENEVER the user wants to release, publish, ship a new version, bump the version, cut a tag, or generate a changelog entry for this package — even if they only say "release it" or "let's publish". Drives the whole local side of the release: derive the next semver version from the commit history, write the CHANGELOG section, sync package.json, run the full verification suite, commit, push, and (only after explicit confirmation) tag — the tag push triggers the GitHub Actions npm-publish workflow. Then open a draft GitHub Release with friendly notes and publish it once CI confirms the npm publish succeeded.

Cut and publish a new npm release of vaultmd. Use this WHENEVER the user wants to release, publish, ship a new version, bump the version, cut a tag, or generate a changelog entry for this package — even if they only say "release it" or "let's publish". Drives the whole local side of the release: derive the next semver version from the commit history, write the CHANGELOG section, sync `package.json`, check and refresh `README.md` for accuracy, run the full verification suite, commit, push, and (only after explicit confirmation) tag — the tag push triggers the GitHub Actions npm-publish workflow. Then open a draft GitHub Release with friendly notes and publish it once CI confirms the npm publish succeeded.

Creates blog posts from rough Russian technical drafts. Translates into clear, natural English while preserving technical accuracy, code examples, and the author's personal voice. Use when creating new blog posts from Russian drafts.