run-ci
/run-ci
Analyze current branch changes with the repo CI detector and run user-selected local CI jobs. Use when the user asks to run, reproduce, or choose local CI checks.
- Author
- shakacode ↗
- Repository
- agent-workflows ↗
- Licence
- MIT
- Last repository change
- 28.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 28.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyze current branch changes with the repo CI detector and run user-selected local CI jobs. Use when the user asks to run, reproduce, or choose local CI checks.
Original author description
Analyze current branch changes with the repo CI detector and run user-selected local CI jobs. Use when the user asks to run, reproduce, or choose local CI checks.
How it works
- Base Handling
- Instructions
- Options
SKILL.md preview
--- name: run-ci description: Analyze current branch changes with the repo CI detector and run user-selected local CI jobs. Use when the user asks to run, reproduce, or choose local CI checks. --- # Run CI Command Analyze the current branch changes and run appropriate CI checks locally. ## Base Handling The repo's pre-push local validation command is `.agents/bin/validate`. It should auto-detect the current PR base branch when the repo supports optimized routing. Do not pass a base-ref argument to it unless that wrapper documents one. Use `.agents/bin/ci-detect` only when you need to inspect the routing decision directly and the script exists. Before running commands, inspect: - `.agents/bin/validate` - `.agents/bin/ci-detect` when present - `.agents/agent-workflow.yml` for `base_branch` and CI policy notes Apply the [delivery coverage contract](../verify/references/verification-evidence.md#delivery-coverage). Execute selection through the trusted-base wrapper or a protected repository entry point. The repository's wrappers define integration and complete promotion invocations; omission retains existing coverage. Missing or invalid routing evidence cannot select reduced checks. ## Instructions 1. First, run `.agents/bin/ci-detect` to inspect what changed when the user asks for routing details and the script exists; otherwise select `.agents/bin/validate` for execution in step 3 2. Preview required checks, omissions, and the selection reason only when the detector has reported them; otherwise obtain them from the wrapper during step 3. Preserve mandatory lint, review, security, and current-head CI requirements. 3. Execute the authorized repository invocation. Resolve a choice with the user only when the request and repository policy leave a material decision open. Promotion requires the documented complete suite; do not invent flags. 4. Report phase, candidate/base identity, selected or full coverage, each required result, and omissions/reason. Selected success does not prove omitted checks passed. 5. Diagnose failed jobs using `/verify`'s existing retry boundary. A stopping or review budget pauses for disposition with failures still blocking; it does not create a successful gate. ## Options - `.agents/bin/validate` - Run local CI based on the repo wrapper contract - Other invocations exist only when the repository's command table documents them. Run selected integration checks or complete promotion checks as that table specifies.
Files in this package (2)
- SKILL.md 2 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named run-ci.
Database snapshot: 13.11.2026 · package version 6e810d855564 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100local-ci
Run GitHub Actions CI locally with Local CI to validate changes before pushing. Use when testing, running checks, or validating code changes. - 100ci
This skill should be used when the user asks to "run CI locally", "ci check", "smoke test", "run ci", "ci smoke", "pre-push check", "verify before PR", "CI を実行", "ローカル CI", or wants to reproduce GitHub Actions CI workflow checks on the local machine. - 100fixing-streamlit-ci
Analyze and fix failed GitHub Actions CI jobs for the current branch/PR. Use when CI checks fail, PR checks show failures, or you need to diagnose lint/type/test errors and verify fixes locally. - 100verify
Run a local verification loop for the current branch before creating or updating a PR, selecting checks from the repo's binstub contract and changed files. Use when asked to verify, test, or prepare PR changes. - 100local-ci
Run this repository's local CI parity commands and `pnpm run ci:local` jobs. Use when validating a change against the same job shapes used in GitHub Actions, choosing the smallest local CI job for a package, workflow, E2E, Metro, devtools, bundle-size, or build-and-test change. - 95reviews
Review the code changes on the current branch. Use when the user asks to review their current work, analyze recent commits, or get a code quality assessment of the active branch against the main branch.