#自動化
Explore public prompts for 自動化. Narrow the topic by medium or change the order.
Showing 1–6 of 6 · Page 1 / 1
Claude Code Hook Recipe: Auto Format + Lint After Every Edit (PostToolUse)
A PostToolUse hook that makes Claude Code automatically run a formatter (Prettier/Black/gofmt) plus a linter every time it edits or writes a file—permanently removing 'inconsistent formatting' as a code review chore.
Codex Skills Mode: Installing Skill Packs and an Autonomous Implementation Loop (cc-sdd)
Uses cc-sdd's --codex-skills install to load reusable skills (SKILL.md) into Codex CLI on demand, and replicates its /kiro-impl autonomous execution loop — a fresh implementer per task, an independent reviewer, and automatic root-cause debugging on failure — so Codex advances steadily through a task list one task at a time.
Codex exec Non-Interactive Mode: Wiring Codex Into a CI Automation Pipeline
Uses codex exec's non-interactive execution plus a restricted sandbox to plug Codex CLI into CI / scripted workflows for unattended tasks like lint fixes, batch refactors, and auto-repair, guarding the safety boundary with approval_policy=never paired with a workspace-write sandbox.
Claude Code Slash Command Designer: One-Click Custom /commands
Turns the checklist or multi-step process you re-paste every time into a custom slash command (.claude/commands/<name>.md, or the newer .claude/skills), with correct frontmatter, $ARGUMENTS parameters, live context pre-injected via `!cmd` (git diff, PR content), and permissions scoped down with allowed-tools.
Claude Code Hooks Builder: Auto Format/Lint/Tests After Every Edit
Uses hooks in .claude/settings.json to automatically run formatting, linting, type-checking, or tests at specific Claude Code lifecycle events (PostToolUse after an edit, PreToolUse before running a command, Stop when wrapping up)—producing correct JSON config plus an executable hook script, with exit code 2 hard-blocking dangerous actions.
Claude Code Skill Factory: Turn Repetitive Workflows Into SKILL.md
Has Claude Code interview you about a repetitive manual process, then produce a fully-structured Agent Skill (SKILL.md) covering name/description/trigger conditions/step-by-step instructions/acceptance criteria/supporting references, and verify it can be triggered automatically as well as invoked via a /slash command.