rielflow

Use when running live credential-backed smoke tests for rielflow Discord Gateway, Telegram Gateway, Matrix, or multi-persona chat workflows through Computer Use. Applies to opening Discord/Telegram/Element or Matrix web UIs, sending natural chat messages or attachments, checking persona routing, default responders, handoffs, history-after-restart behavior, and collecting rielflow event/session/reply evidence without exposing credentials.

Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `codex-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.

Use when creating, modifying, reviewing, or validating rielflow workflow bundles. Applies to step-addressed workflow.json authoring, node payload files, prompt files, built-in node add-ons, cross-workflow transitions, manager/worker routing, and portable workflows under a workflow root.

Use when writing TypeScript code that interacts with dependencies, handles credentials, executes child processes, or manages configuration. Provides Shai-Hulud supply chain attack countermeasures at the code level including safe dependency usage, credential handling, subprocess hardening, and runtime integrity patterns.

Use when writing, reviewing, or refactoring TypeScript code. Provides type safety patterns, error handling, project layout, and async programming guidelines.

Use when the user asks Codex to security-check current source code, run secure code review, find and fix source security issues, run deterministic SAST or dependency/security scans, or loop fixes until security findings are resolved through the packaged `codex-source-security-check-loop` Rielflow workflow.

Use when preparing, publishing, verifying, or troubleshooting a rielflow release through GitHub release assets and the tacogips/tap Homebrew formula. Applies to building standalone Homebrew archives, rendering Formula/rielflow.rb, updating the sibling homebrew-tap repository, brew smoke tests, release rollback checks, and post-release install verification.

Use when bumping rielflow workspace package versions without publishing a release. Applies to requests such as bump to a requested version, version bump only, prepare version metadata, or updating rielflow package.json and bun.lock versions. Stops before tags, GitHub releases, archive builds, Homebrew tap updates, npm publishing, commits, or pushes unless the user explicitly asks for those actions.

Use when creating, renaming, editing, reviewing, or validating Docker Compose or Podman Compose files such as compose.yaml, compose.*.yaml, docker-compose.yml, docker-compose.yaml, compose.yml, and service-specific Compose files. Applies to modern Compose filename conventions, .yaml/.yml extension standardization, service/network/volume definitions, port mappings, environment variables, secrets, healthchecks, and docker compose or podman-compose verification commands.

Use when cleaning managed Git worktrees for the current package. Inspects ../worktrees/{packagename}, keeps worktrees whose branch commits are not merged into the default branch, and removes merged worktree directories with git worktree remove.