create-pr

Files (3)

• SKILL.md
• openai.yaml · agents/
• check-skill-scripts.sh · scripts/

SKILL.md (first lines)

# Create PR

Use this repo-local skill when opening a new PR for this repository. It only adds the repo-specific gates before handing off to `$managing-gitcode-prs`.

## When To Use

- Opening a new PR for the current repository
- Enforcing this repo's pre-PR checks and fresh-branch rule

Do not use this skill just to inspect, list, or update an existing PR. Use `$managing-gitcode-prs` for those tasks.

## Required Gates

- `GC_TOKEN` must be set before the final PR creation step.
- A new PR must come from a fresh topic branch. Do not open it from `main`, `master`, `dev`, or another reused branch.
- Finish with a clean working tree and a pushed branch.
- Run exactly these checks from the repository root:

```bash
uv run --group dev ruff check
uv run pyright
uv run python -m pytest -q --tb=short --no-header -p no:warnings tests/
bash ./scripts/check-skill-scripts.sh
```

Only run the strict skill-script pyright check on `skills/*/scripts/*.py` files changed in this branch (diff against `origin/main`). If the diff produces no matching files, the loop is a no-op. If any required command fails, stop, fix it, and rerun the full set before creating the PR.

## PR Description Style

- Write short, bullet-point key points only. Do not include long prose, verification tables, or redundant summaries.
- The description should make it clear at a glance what changed and why.

## Final Handoff

Use `$managing-gitcode-prs` for the actual PR creation step. Keep GitCode-specific flags and API details there instead of duplicating them here.

From Piagari/helix, Apache-2.0.

More from Piagari/helix