pr-ready

Files (1)

• SKILL.md

SKILL.md (first lines)

# PR Ready

Validate and mark a PR ready for review. Run quality gates before flipping.

## Inputs

PR number or URL. Optional: `-Fast` (lint + unit tests only), `-DryRun` (print actions only).

## Workflow

1. **Run validation** — Read the consuming project's root AGENTS.md and any workflow document it names (convention: `docs/agents/workflow.md`, relative to the project root). Prefer `VALIDATE_COMMAND` or `RUN_ALL_TESTS_COMMAND`, running the complete gate once. Resolve required commands before execution; report missing configuration instead of guessing or skipping a gate. If separate gates are required, resolve:
   - `{{LINT_COMMAND}}`
   - `{{RUN_UNIT_TESTS_COMMAND}}`
   - `{{RUN_ALL_TESTS_COMMAND}}`
   - `{{SMOKE_TEST_COMMAND}}` (optional)

   Default: the complete delivery gate. `-Fast` gives focused feedback only; it cannot mark the PR ready unless the project explicitly permits it as the delivery gate. Do not rerun an identical command under multiple mappings.

2. **Check CI** — Run `gh pr checks <pr> --watch`. Wait for green.

3. **Post summary** — Comment on the PR with what ran and whether it passed:
   ```
   gh pr comment <pr> --body "..."
   ```

4. **Mark ready** — Only if all gates pass and CI is green:
   ```
   gh pr ready <pr>
   ```

## Notes

- If any gate fails, post a failing summary. Do not mark ready.
- If CI is not green, do not mark ready. Wait or report the failure.

From LightForgeLabsStudio/AIDE, MIT.

More from LightForgeLabsStudio/AIDE