Jxck

Update project versions and release tag in one consistent flow (Cargo.toml, xtask, docs, and git tag).

Run a repository-wide maintenance pass before merge/release. Covers cleanup, formatting, tests, docs, security, and CI checks.

Use when changing Rust code paths that return errors or log failures. Ensures errors are actionable, consistent, and safe.

Use before merging security-relevant Rust changes. Catches common local-service security regressions.

Use when adding or modifying tests. Ensures behavior changes are covered with focused tests and fast feedback.

Use when making code or documentation changes in this repository. Provides consistent workflow and validation steps.

Prevent dev-environment values (origins, ports, hosts, absolute paths, secrets) from leaking into build artifacts, generated code, or production output. Use whenever writing or reviewing build scripts / codegen, adding a URL / port / hostname / origin literal, branching on dev vs prod, configuring CORS or crossorigin attributes, or when generated files (*.gen.*, dist output, feeds, sitemaps) embed any absolute URL. Trigger proactively — this class of bug ships silently and is only noticed in production.

Working discipline for hard tasks — decompose, verify, and decide what to do next. Use whenever a task is non-trivial: the approach is not obvious, it spans multiple steps or files, it involves debugging an unknown cause, an irreversible or production-facing change, or the user says it is hard/complex/stuck. Also use when starting work that a strong model (Opus 4.8+) is delegated precisely because it is difficult. Do not wait for the user to ask for "planning" — apply this protocol proactively at the start of any such task.

Audit alignment between AGENTS.md and repo-local shared skills under .agents/skills. Invoke explicitly only; do not auto-trigger on generic agent or skill maintenance requests.

Create and iterate on implementation plans under .agents/plan/ so multiple agents (Claude / Codex / 他) can review each other's drafts. Use when entering plan mode, drafting an implementation plan, or reviewing an existing plan.

Create install scripts under ./install/install-<name>.sh following this dotfiles repo's build/install conventions (brew vs self-build, pkg/local layout, OS branching).

Sync and harden command permissions between .claude/settings.json and .codex/rules/default.rules in this dotfiles repo.

Write git commit messages for this repository following the `[area]` prefix convention. Use when composing or reviewing a commit message in jxck.io.

Proofread and review articles under blog.jxck.io/entries following the repository's editorial policy. Use when asked to review, proofread, or 校正 a draft or published article.