Decide whether a completed Matryca change belongs in CHANGELOG.md and add one concise Unreleased entry when required. Use before concluding runtime, security, architecture, integration, performance, operator, or public-contract changes.
Keep Matryca environment-variable code, defaults, UI mappings, .env.example, coverage tests, and changelog synchronized. Use when adding, renaming, deprecating, exposing, or changing any environment variable or default.
Apply Matryca maintainer standards for GitHub issues, pull requests, branches, reviews, merges, milestones, tags, releases, and remote comments. Use before any GitHub-facing action or artifact.
Choose safe direct-file versus Local HTTP API access for Logseq. Use when changing graph reads, writes, background indexing, live Logseq integration, authentication, or JSON-RPC communication.
Apply Matryca's Logseq OG outliner, block/property, namespace, and Markdown semantics. Use for graph-content generation, Logseq block or page-property changes, namespace handling, or code that transforms vault content.
Maintain Matryca prompt builders, Tier-2 OpenSpec fragments, generated SYSTEMPROMPT.md, prompt hashes, MCP tool docstrings, and llms.txt synchronization. Use for any prompt or MCP tool-contract change.
Prepare, cut, verify, tag, or publish a Matryca semantic-version release. Use for version bumps, changelog finalization, release notes, build metadata, tags, GitHub Releases, or PyPI publication.