Pr Creator

1---2name: pr-creator3description:4  Use this skill when asked to create a pull request (PR). It ensures all PRs5  follow the repository's established templates and standards.6---7 8# Pull Request Creator9 10This skill guides the creation of high-quality Pull Requests that adhere to the11repository's standards.12 13## Workflow14 15Follow these steps to create a Pull Request:16 171.  **Branch Management**: **CRITICAL:** Ensure you are NOT working on the18    `main` branch.19    - Run `git branch --show-current`.20    - If the current branch is `main`, you MUST create and switch to a new21      descriptive branch:22      ```bash23      git checkout -b <new-branch-name>24      ```25 262.  **Commit Changes**: Verify that all intended changes are committed.27    - Run `git status` to check for unstaged or uncommitted changes.28    - If there are uncommitted changes, stage and commit them with a descriptive29      message before proceeding. NEVER commit directly to `main`.30      ```bash31      git add .32      git commit -m "type(scope): description"33      ```34 353.  **Locate Template**: Search for a pull request template in the repository.36    - Check `.github/pull_request_template.md`37    - Check `.github/PULL_REQUEST_TEMPLATE.md`38    - If multiple templates exist (e.g., in `.github/PULL_REQUEST_TEMPLATE/`),39      ask the user which one to use or select the most appropriate one based on40      the context (e.g., `bug_fix.md` vs `feature.md`).41 424.  **Read Template**: Read the content of the identified template file.43 445.  **Draft Description**: Create a PR description that strictly follows the45    template's structure.46    - **Headings**: Keep all headings from the template.47    - **Checklists**: Review each item. Mark with `[x]` if completed. If an item48      is not applicable, leave it unchecked or mark as `[ ]` (depending on the49      template's instructions) or remove it if the template allows flexibility50      (but prefer keeping it unchecked for transparency).51    - **Content**: Fill in the sections with clear, concise summaries of your52      changes.53    - **Related Issues**: Link any issues fixed or related to this PR (e.g.,54      "Fixes #123").55 566.  **Preflight Check**: Before creating the PR, run the workspace preflight57    script to ensure all build, lint, and test checks pass.58    ```bash59    npm run preflight60    ```61    If any checks fail, address the issues before proceeding to create the PR.62 637.  **Push Branch**: Push the current branch to the remote repository.64    **CRITICAL SAFETY RAIL:** Double-check your branch name before pushing.65    NEVER push if the current branch is `main`.66    ```bash67    # Verify current branch is NOT main68    git branch --show-current69    # Push non-interactively70    git push -u origin HEAD71    ```72 738.  **Create PR**: Use the `gh` CLI to create the PR. To avoid shell escaping74    issues with multi-line Markdown, write the description to a temporary file75    first.76    ```bash77    # 1. Write the drafted description to a temporary file78    # 2. Create the PR using the --body-file flag79    gh pr create --title "type(scope): succinct description" --body-file <temp_file_path>80    # 3. Remove the temporary file81    rm <temp_file_path>82    ```83    - **Title**: Ensure the title follows the84      [Conventional Commits](https://www.conventionalcommits.org/) format if the85      repository uses it (e.g., `feat(ui): add new button`,86      `fix(core): resolve crash`).87 88## Principles89 90- **Safety First**: NEVER push to `main`. This is your highest priority.91- **Compliance**: Never ignore the PR template. It exists for a reason.92- **Completeness**: Fill out all relevant sections.93- **Accuracy**: Don't check boxes for tasks you haven't done.