sc-ci-automation
Run CI quality gates with optional auto-fix and PR creation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Run CI quality gates with optional auto-fix and PR creation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Set up a repo-local just task runner with a root Justfile, optional .just/ helper scripts, and curated help, build, fmt, lint, test, and ci recipes. Use when a repo needs just, a Justfile, .just helpers, or when the user mentions task automation, "just build", "just lint", "just fmt", or dropping in a just system.
Create or harden CLIs intended primarily for AI or system consumption and secondarily for humans. Use when designing or implementing a JSON-first CLI with an MCP-ready contract seam, where every command supports machine output, errors are typed and actionable, mutating commands are auditable via corresponding read commands, and external integrations need simulator-backed testing. Do not use for human-first shell utilities, one-off scripts, or text-only CLIs.
Design stateful simulators for AI-facing CLIs that integrate with devices, networks, services, or databases. Use when a CLI needs realistic simulator-backed testing, configurable fault injection, persistent state, and a swappable adapter boundary so the same business logic runs against live and simulated backends. Do not use for shallow mocks, stateless test doubles, or CLIs with no external integration.
Critically review an existing CLI, MCP wrapper, or CLI plan for AI-first contract quality. Use when evaluating whether a CLI is JSON-first, has an MCP-ready contract seam without JSON reshaping, auditably models state changes, uses stateful simulator-backed testing for external integrations, and returns typed actionable errors. Do not use for general style review or human-first shell UX review.
Run Codex tasks via the ai_cli Task Tool runner.
Harden coding, QA, and orchestration agent prompts so they fix issues autonomously instead of letting findings pass through as minor, pre-existing, non-blocking, or technical debt. Use when editing existing agent prompts, review instructions, or orchestration workflows to remove permissive issue-handling behavior and tighten escalation criteria.
| name | sc-ci-automation |
| version | 0.12.0 |
| description | Run CI quality gates with optional auto-fix and PR creation. |
| entry_point | /sc-ci-automation |
Coordinates pull → build → test → fix → PR. Keeps instructions lean; heavy details live in references and contracts file. Agent Runner is required for all agent calls (registry-enforced, audited).
/sc-ci-automation (flags: --build, --test, --dest, --src, --allow-warnings, --patch, --yolo, --help)ci-validate-agent: pre-flight checks (clean repo, config present, auth available)ci-pull-agent: pull target branch, handle simple conflictsci-build-agent: run build, classify failuresci-test-agent: run tests, classify failures/warningsci-fix-agent: apply straightforward fixesci-root-cause-agent: summarize unresolved issues, recommend actionsci-pr-agent: commit/push/PR when gates passci-validate-agentci-pull-agent (dest inferred from tracking; --dest overrides)ci-build-agentci-fix-agent (only straightforward fixes), repeatci-test-agentci-fix-agent if straightforward, else ci-root-cause-agent--yolo): Agent Runner → ci-pr-agent to commit/push/PRPreferred: .claude/ci-automation.yaml (fallback: .claude/config.yaml) with upstream_branch, build_command, test_command, warn_patterns, allow_warnings, auto_fix_enabled, pr_template_path, repo_root. Detect stack (e.g., .NET/Python/Node) and prompt to save suggested commands.
--yolo: allow commit/push/PR after gates pass.--allow-warnings or config override.--dest main provided..claude/state/logs/ci-automation/..claude/references/ci-automation-commands.md.claude/references/ci-automation-checklists.md.claude/references/ci-automation-contracts.md