jclem

Guide to setting up third-party authentication for a Notion Worker. Covers external-service API keys / personal access tokens and OAuth. Use when the worker needs credentials for a non-Notion API, not for Notion API tokens or `ntn login`.

Diagnose a failing or misbehaving sync — fetch run logs, identify errors, cross-reference with code, and suggest fixes

Comprehensive guide to building Notion Workers syncs — covers the two-sync architecture (backfill+delta), replace mode, pagination, consistency buffers, pacers, deletion strategies, and common pitfalls. Auto-loads when sync-related work is detected.

Scaffold a new sync capability with guided setup — asks about data source, mode, pagination, and cursor design, then generates working code

Review a sync capability for common bugs — cursor advancement, pagination termination, state persistence, bi-modal correctness, consistency buffers, and deletion handling

Add or update Neovim 0.12 language-server configurations using native vim.lsp APIs, nvim-lspconfig defaults, vim.pack, and Mise-managed server executables. Use when adding a language server, migrating an LSP spec, changing server settings, enabling LSP formatting, or validating LSP behavior in the dotfiles Neovim configuration.

Add, configure, update, or remove Neovim 0.12 plugins in the dotfiles repository using the native vim.pack package manager. Use when introducing a plugin, replacing a plugin, adding plugin dependencies or build hooks, configuring native plugin loading, or maintaining the Neovim package lockfile.

Write and review Git commit messages for the dotfiles repository. Use when drafting a commit message, creating a commit, or checking whether commit text follows this repository's area-prefixed style.

Create, rewrite, and review Fish functions for the dotfiles repository using its standard file layout, documentation, argument parsing, long-form options, error handling, safety checks, and validation. Use whenever adding or modifying a file under dot_config/fish/functions.

Open GitHub pull requests from local branches with repository-appropriate tooling and a required Notion issue ID title prefix. Use when the user asks to open, create, draft, publish, or prepare a pull request, especially in the Envelope repository where PR titles must begin with an issue ID from the Notion Issues database at https://www.notion.so/jclem/35e6361404d980d9aac6c4c12e141442?v=35e6361404d980989431000c25353ced&source=copy_link.

Use when reading, editing, reviewing, or maintaining GitHub Actions workflows or composite actions. Always use the `gh actions-versions` GitHub CLI extension from `https://github.com/jclem/gh-actions-versions` to keep external action references pinned to exact SHAs, verify that pins match their version comments, periodically check whether workflow actions are on the latest available versions, and suggest updates when they are stale.

Write or review Git commit messages using a strict house style. Use when drafting commit messages, creating commits, reviewing proposed commit text, or explaining the preferred commit-message format.

Create and refine git commits, amend history, and push branches for requested code changes. Use when a user asks to craft, rewrite, or improve commit messages, stage specific files, amend previous commits, force-push updated commits, or enforce commit message formatting.