openase

Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.

Write workflow harness files that define role, status semantics, feedback loops, and durable delivery rules for disposable ticket workspaces.

Clarify ambiguous requests with a focused, Socratic interview before planning or implementation.

Review behavior, risk, performance, and test coverage before style nits.

Review trust boundaries, auth, input handling, secrets, and dependency risk before release.

Turn a clarified spec into milestone-oriented tickets, dependency edges, and stage-gated delivery lanes.

Platform operations for tickets, projects, and runtime coordination inside OpenASE.

Diagnose and strengthen a repository's harness layer: AGENTS.md rules, knowledge layout, architecture boundaries, lint and type gates, API and generated-client contracts, test scaffolding, structured logging, and technical-debt tracking. Use when Codex needs to audit drift-prone semantics that are repeated across code, docs, schemas, generated artifacts, frontend/backend boundaries, or CI, then design or implement guardrails with progressive disclosure and zero-tolerance contract checks.

Diagnose and repair OpenASE CLI access in local bootstrap mode. Use when protected `openase` commands fail because the CLI is missing a local human session, has a stale `~/.openase/human-session.json`, is missing CSRF state, or needs a fresh `openase auth bootstrap login`.

Build and locally redeploy OpenASE from the current branch, including web static assets and the Go binary, then restart the local service and verify health. Use when asked to compile, deploy, restart, or locally upgrade the current checkout.

Write concise Conventional Commit messages that match the actual scope of the change.

Prepare a crisp pull request summary with scope, validation, and rollout notes.

Install Claude Code on a target machine and verify the CLI is available for remote execution.

Install the Codex CLI on a target machine and verify it can start successfully.

Land a reviewed change only after CI and branch-state checks pass.

Sync with the latest remote branch before coding or pushing, keeping history linear.

Push verified changes carefully and avoid destructive history rewrites.

Install or repair the GitHub CLI and confirm authentication status on the target machine.

Install or repair git plus the minimum identity and credential configuration needed for agent work.

Maintain the persistent ticket work log comment on the current ticket and use it as the execution log.

Design focused tests that cover the real behavior contract and key edge cases.

Land an OpenASE PR by syncing with main, resolving conflicts, waiting for CI, addressing review feedback, and squash-merging when green.

Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.

Push current branch changes to origin and create or update the corresponding pull request for OpenASE; use when asked to push, publish updates, or create a pull request.

Create a detailed GitHub issue for OpenASE and add it to the OpenASE Automation project with a caller-selected status (defaults to Todo). Use when asked to report a bug, deployment regression, local repro, or design task into GitHub with reproducible evidence and project binding.