[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-google-gemini-gemini-cli-.gemini-skills-pr-creator":3},{"error":4,"detail":5,"metadata":24,"markdownContent":25,"rawMarkdown":21},false,{"repo_full_name":6,"owner":7,"repo_name":8,"repo_forks":9,"skill_path":10,"repo_stars":11,"name":12,"category_id":13,"description":14,"file_tree":15,"skill_md_content":21,"skill_id":22,"skill_key":23},"google-gemini/gemini-cli","google-gemini","gemini-cli",12405,".gemini/skills/pr-creator",98300,"pr-creator",1,"",[16],{"name":17,"path":18,"size":19,"type":20},"SKILL.md",".gemini/skills/pr-creator/SKILL.md",3700,"file","---\nname: pr-creator\ndescription:\n  Use this skill when asked to create a pull request (PR). It ensures all PRs\n  follow the repository's established templates and standards.\n---\n\n# Pull Request Creator\n\nThis skill guides the creation of high-quality Pull Requests that adhere to the\nrepository's standards.\n\n## Workflow\n\nFollow these steps to create a Pull Request:\n\n1.  **Branch Management**: **CRITICAL:** Ensure you are NOT working on the\n    `main` branch.\n    - Run `git branch --show-current`.\n    - If the current branch is `main`, you MUST create and switch to a new\n      descriptive branch:\n      ```bash\n      git checkout -b \u003Cnew-branch-name>\n      ```\n\n2.  **Commit Changes**: Verify that all intended changes are committed.\n    - Run `git status` to check for unstaged or uncommitted changes.\n    - If there are uncommitted changes, stage and commit them with a descriptive\n      message before proceeding. NEVER commit directly to `main`.\n      ```bash\n      git add .\n      git commit -m \"type(scope): description\"\n      ```\n\n3.  **Locate Template**: Search for a pull request template in the repository.\n    - Check `.github/pull_request_template.md`\n    - Check `.github/PULL_REQUEST_TEMPLATE.md`\n    - If multiple templates exist (e.g., in `.github/PULL_REQUEST_TEMPLATE/`),\n      ask the user which one to use or select the most appropriate one based on\n      the context (e.g., `bug_fix.md` vs `feature.md`).\n\n4.  **Read Template**: Read the content of the identified template file.\n\n5.  **Draft Description**: Create a PR description that strictly follows the\n    template's structure.\n    - **Headings**: Keep all headings from the template.\n    - **Checklists**: Review each item. Mark with `[x]` if completed. If an item\n      is not applicable, leave it unchecked or mark as `[ ]` (depending on the\n      template's instructions) or remove it if the template allows flexibility\n      (but prefer keeping it unchecked for transparency).\n    - **Content**: Fill in the sections with clear, concise summaries of your\n      changes.\n    - **Related Issues**: Link any issues fixed or related to this PR (e.g.,\n      \"Fixes #123\").\n\n6.  **Preflight Check**: Before creating the PR, run the workspace preflight\n    script to ensure all build, lint, and test checks pass.\n    ```bash\n    npm run preflight\n    ```\n    If any checks fail, address the issues before proceeding to create the PR.\n\n7.  **Push Branch**: Push the current branch to the remote repository.\n    **CRITICAL SAFETY RAIL:** Double-check your branch name before pushing.\n    NEVER push if the current branch is `main`.\n    ```bash\n    # Verify current branch is NOT main\n    git branch --show-current\n    # Push non-interactively\n    git push -u origin HEAD\n    ```\n\n8.  **Create PR**: Use the `gh` CLI to create the PR. To avoid shell escaping\n    issues with multi-line Markdown, write the description to a temporary file\n    first.\n    ```bash\n    # 1. Write the drafted description to a temporary file\n    # 2. Create the PR using the --body-file flag\n    gh pr create --title \"type(scope): succinct description\" --body-file \u003Ctemp_file_path>\n    # 3. Remove the temporary file\n    rm \u003Ctemp_file_path>\n    ```\n    - **Title**: Ensure the title follows the\n      [Conventional Commits](https://www.conventionalcommits.org/) format if the\n      repository uses it (e.g., `feat(ui): add new button`,\n      `fix(core): resolve crash`).\n\n## Principles\n\n- **Safety First**: NEVER push to `main`. This is your highest priority.\n- **Compliance**: Never ignore the PR template. It exists for a reason.\n- **Completeness**: Fill out all relevant sections.\n- **Accuracy**: Don't check boxes for tasks you haven't done.\n","8e348735-628a-5264-8e98-993c1a714124","google-gemini-gemini-cli-.gemini-skills-pr-creator",{"name":12},"\u003Ch1>Pull Request Creator\u003C/h1>\n\u003Cp>This skill guides the creation of high-quality Pull Requests that adhere to the\nrepository's standards.\u003C/p>\n\u003Ch2>Workflow\u003C/h2>\n\u003Cp>Follow these steps to create a Pull Request:\u003C/p>\n\u003Col>\n\u003Cli>\u003Cp>\u003Cstrong>Branch Management\u003C/strong>: \u003Cstrong>CRITICAL:\u003C/strong> Ensure you are NOT working on the\n\u003Ccode>main\u003C/code> branch.\u003C/p>\n\u003Cul>\n\u003Cli>Run \u003Ccode>git branch --show-current\u003C/code>.\u003C/li>\n\u003Cli>If the current branch is \u003Ccode>main\u003C/code>, you MUST create and switch to a new\ndescriptive branch:\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">git checkout -b <new-branch-name>\u003C/code>\u003C/pre>\u003C/div>\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Commit Changes\u003C/strong>: Verify that all intended changes are committed.\u003C/p>\n\u003Cul>\n\u003Cli>Run \u003Ccode>git status\u003C/code> to check for unstaged or uncommitted changes.\u003C/li>\n\u003Cli>If there are uncommitted changes, stage and commit them with a descriptive\nmessage before proceeding. NEVER commit directly to \u003Ccode>main\u003C/code>.\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">git add .\ngit commit -m \u003Cspan class=\"hljs-string\">"type(scope): description"\u003C/span>\u003C/code>\u003C/pre>\u003C/div>\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Locate Template\u003C/strong>: Search for a pull request template in the repository.\u003C/p>\n\u003Cul>\n\u003Cli>Check \u003Ccode>.github/pull_request_template.md\u003C/code>\u003C/li>\n\u003Cli>Check \u003Ccode>.github/PULL_REQUEST_TEMPLATE.md\u003C/code>\u003C/li>\n\u003Cli>If multiple templates exist (e.g., in \u003Ccode>.github/PULL_REQUEST_TEMPLATE/\u003C/code>),\nask the user which one to use or select the most appropriate one based on\nthe context (e.g., \u003Ccode>bug_fix.md\u003C/code> vs \u003Ccode>feature.md\u003C/code>).\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Read Template\u003C/strong>: Read the content of the identified template file.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Draft Description\u003C/strong>: Create a PR description that strictly follows the\ntemplate's structure.\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>Headings\u003C/strong>: Keep all headings from the template.\u003C/li>\n\u003Cli>\u003Cstrong>Checklists\u003C/strong>: Review each item. Mark with \u003Ccode>[x]\u003C/code> if completed. If an item\nis not applicable, leave it unchecked or mark as \u003Ccode>[ ]\u003C/code> (depending on the\ntemplate's instructions) or remove it if the template allows flexibility\n(but prefer keeping it unchecked for transparency).\u003C/li>\n\u003Cli>\u003Cstrong>Content\u003C/strong>: Fill in the sections with clear, concise summaries of your\nchanges.\u003C/li>\n\u003Cli>\u003Cstrong>Related Issues\u003C/strong>: Link any issues fixed or related to this PR (e.g.,\n"Fixes #123").\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Preflight Check\u003C/strong>: Before creating the PR, run the workspace preflight\nscript to ensure all build, lint, and test checks pass.\u003C/p>\n\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">npm run preflight\u003C/code>\u003C/pre>\u003C/div>\u003Cp>If any checks fail, address the issues before proceeding to create the PR.\u003C/p>\n\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Push Branch\u003C/strong>: Push the current branch to the remote repository.\n\u003Cstrong>CRITICAL SAFETY RAIL:\u003C/strong> Double-check your branch name before pushing.\nNEVER push if the current branch is \u003Ccode>main\u003C/code>.\u003C/p>\n\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">\u003Cspan class=\"hljs-comment\"># Verify current branch is NOT main\u003C/span>\ngit branch --show-current\n\u003Cspan class=\"hljs-comment\"># Push non-interactively\u003C/span>\ngit push -u origin HEAD\u003C/code>\u003C/pre>\u003C/div>\u003C/li>\n\u003Cli>\u003Cp>\u003Cstrong>Create PR\u003C/strong>: Use the \u003Ccode>gh\u003C/code> CLI to create the PR. To avoid shell escaping\nissues with multi-line Markdown, write the description to a temporary file\nfirst.\u003C/p>\n\u003Cdiv class=\"md-code-block\">\u003Cdiv class=\"md-code-lang\">bash\u003C/div>\u003Cpre>\u003Ccode class=\"hljs language-bash\">\u003Cspan class=\"hljs-comment\"># 1. Write the drafted description to a temporary file\u003C/span>\n\u003Cspan class=\"hljs-comment\"># 2. Create the PR using the --body-file flag\u003C/span>\ngh \u003Cspan class=\"hljs-built_in\">pr\u003C/span> create --title \u003Cspan class=\"hljs-string\">"type(scope): succinct description"\u003C/span> --body-file <temp_file_path>\n\u003Cspan class=\"hljs-comment\"># 3. Remove the temporary file\u003C/span>\n\u003Cspan class=\"hljs-built_in\">rm\u003C/span> <temp_file_path>\u003C/code>\u003C/pre>\u003C/div>\u003Cul>\n\u003Cli>\u003Cstrong>Title\u003C/strong>: Ensure the title follows the\n\u003Ca href=\"https://www.conventionalcommits.org/\">Conventional Commits\u003C/a> format if the\nrepository uses it (e.g., \u003Ccode>feat(ui): add new button\u003C/code>,\n\u003Ccode>fix(core): resolve crash\u003C/code>).\u003C/li>\n\u003C/ul>\n\u003C/li>\n\u003C/ol>\n\u003Ch2>Principles\u003C/h2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Safety First\u003C/strong>: NEVER push to \u003Ccode>main\u003C/code>. This is your highest priority.\u003C/li>\n\u003Cli>\u003Cstrong>Compliance\u003C/strong>: Never ignore the PR template. It exists for a reason.\u003C/li>\n\u003Cli>\u003Cstrong>Completeness\u003C/strong>: Fill out all relevant sections.\u003C/li>\n\u003Cli>\u003Cstrong>Accuracy\u003C/strong>: Don't check boxes for tasks you haven't done.\u003C/li>\n\u003C/ul>\n"]