#automation
5 articles
-
Hand GitHub work to Codex Cloud, and what changed about building an environment
Using Codex Cloud from ChatGPT: creating an environment from Work in > Cloud, the install script and start skill Codex writes for you, sending tasks, and reviewing the result.
-
Run Claude Code in GitHub Actions with claude-code-action
Set up the official claude-code-action so @claude in an issue or PR comment makes changes, plus the automated review workflow, who is allowed to trigger runs, and how to cap cost.
-
Run lint after every edit in Claude Code: a PostToolUse hook on Edit|Write|MultiEdit
A PostToolUse hook with matcher "Edit|Write|MultiEdit" runs Prettier, ESLint or ruff after every edit. Read the path from tool_input.file_path and feed failures back to Claude.
-
claude -p: run Claude Code non-interactively in scripts and CI (--output-format json, --allowedTools)
Use claude -p "prompt" for non-interactive mode: pipe stdin, get JSON with --output-format json, pre-approve tools with --allowedTools, cap cost with --max-turns. Works in cron/CI.
-
Create your own slash commands in Claude Code with a single Markdown file
Define /review or /commit as a skill in .claude/skills/, how that differs from .claude/commands/, passing arguments with $ARGUMENTS and $1, and embedding Bash output in the prompt.