[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EJC4PR6BMC5MVE2C8PMZZJ":3,"skill-same:01M7EJC4PR6BMC5MVE2C8PMZZJ":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7EJC4PR6BMC5MVE2C8PMZZJ","oak-pr-create",null,"Writes a pull request title and description that explain what a change does and why, with steps to test it, then opens or updates the pull request once the user approves them. Use when opening, creating or updating a pull request, or when asked to write or improve a PR title, description or testing instructions.","oaknational\u002Foak-agent-skills","oaknational","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63889701?v=4","01M71E8KA6A3R1XEZH7NVDPNYK","Oak National Academy","01M7EJBV1G62V115Z34X72Q938",0,"MIT","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcentral\u002Foak-pr-create\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: oak-pr-create\ndescription: Writes a pull request title and description that explain what a change does and why, with steps to test it, then opens or updates the pull request once the user approves them. Use when opening, creating or updating a pull request, or when asked to write or improve a PR title, description or testing instructions.\nlicense: MIT\nmetadata:\n  owner: '@oaknational\u002Fskills-maintainers'\n  updated: '2026-10-27'\n---\n\n# Creating a pull request\n\nWrite a pull request that a reviewer can understand, test and approve without asking the author anything. The title says what the change does; the description says briefly why, and how to check it.\n\n## Before you write\n\n1. Check the branch. Stop if it's the default branch, or if it has no commits ahead of the branch it will merge into. If there are uncommitted changes, ask whether to commit them first. If the branch already has a pull request (`gh pr view`), update that one instead of opening another: see [Updating a pull request](#updating-a-pull-request).\n2. Read the repository's `AGENTS.md` for its conventions, such as ticket references or required sections.\n3. Look for a pull request template, usually `.github\u002Fpull_request_template.md`. If there is one, fill it in: use its sections, in its order, instead of the structure below.\n4. Read the whole change against the branch it will merge into, for example with `git diff main...HEAD`, and read the commit messages.\n5. Find the reason for the change: the linked issue, the conversation that led to it, or the author's explanation. If you can't tell why the change was made, ask rather than invent a reason.\n\n## The title\n\nUse a [Conventional Commit](https:\u002F\u002Fwww.conventionalcommits.org\u002F) title, `type(scope): summary`, because many of our repositories squash-merge pull requests and the title becomes the commit on `main`. Write the summary in the imperative and lower case, without a full stop, such as `feat(search): add lesson filters`. Add `!` for a breaking change, and keep the title under about 72 characters. If the repository's `AGENTS.md` doesn't say whether titles include a ticket ID, ask the user rather than guessing from past titles.\n\n## The description\n\nCover these two things, in this order. [Writing the description](references\u002Fpr-description.md) explains each one, with an example.\n\n1. **What and why.** Two sentences, about 50 words: the problem or the old behaviour, then what the change does. For two or more separate changes, one line that sums them up, then a short bullet for each. Link the issue.\n2. **Testing instructions.** [Testing instructions](references\u002Ftesting-instructions.md) a reviewer can follow. If the change is user-facing, always include them, as explicit, plain-English steps QA can follow, each with what they should see.\n\nLeave out anything the diff, the ticket or CI already shows. Add test evidence only when CI can't show it, in one line with a link.\n\n## Rules\n\n- Only claim what's true. If something wasn't tested, say so.\n- Never include secrets, credentials, personal data or internal links that shouldn't be public. Many of our repositories are public.\n- Link tickets and issues. Never leave a bare ticket number.\n- If the template has a checklist, leave its items for the author to tick, and don't strike through any that could apply.\n- For screenshots, leave a placeholder for the author, or write \"N\u002FA\" with a reason of a few words. Give every image alt text that says what it shows.\n- Write in plain British English for someone who hasn't seen the work. Define anything a reviewer outside the team might not know.\n\n## Opening the pull request\n\nPushing and opening a pull request are visible to other people, so never do either without the user's approval.\n\n1. Run the repository's checks, such as formatting, linting, type checking and tests, using the commands in `AGENTS.md`. If one fails, stop, show its output and offer to fix it. Report which checks ran, and never say a check passed if it didn't run. If the branch changes after the checks ran, run them again before pushing.\n2. Show the user the title, the description, the branch it merges into, the current branch and the commits it contains. Revise them as the user asks, showing the whole updated version each time, until they clearly approve it. Silence or a vague reply isn't approval. Then ask whether to push and open it, and whether as a draft, and don't go on until they say yes.\n3. Push only the current branch: `git push -u origin HEAD`.\n4. Open the pull request with the GitHub CLI, passing the description from a file so the shell can't change it: `gh pr create --title \"\u003Ctitle>\" --body-file \u003Cfile>`. Add `--draft` if the user asked for one, and `--base \u003Cbranch>` if it doesn't merge into the default branch.\n5. Don't request reviewers or add assignees unless the user asks you to.\n6. Give the user the pull request's link.\n7. Offer to watch its CI checks. Only watch if the user says yes. Run `gh pr checks \u003Cnumber> --watch`, in the background if you can, so the user isn't blocked. When the checks finish, say which passed and which failed, and offer to investigate any failure. If they're still running after about 15 minutes, stop watching, say so, and offer to keep going.\n\nIf `gh` isn't installed or signed in, give the user the title and description to paste instead.\n\n## Updating a pull request\n\nWhen the change grows or its approach changes after review, update the title and description so they still describe what will merge. Show the user the new version and wait for their approval, as when opening one, then apply it with `gh pr edit --title \"\u003Ctitle>\" --body-file \u003Cfile>`.\n","# Creating a pull request\n\nWrite a pull request that a reviewer can understand, test and approve without asking the author anything. The title says what the change does; the description says briefly why, and how to check it.\n\n## Before you write\n\n1. Check the branch. Stop if it's the default branch, or if it has no commits ahead of the branch it will merge into. If there are uncommitted changes, ask whether to commit them first. If the branch already has a pull request (`gh pr view`), update that one instead of opening another: see [Updating a pull request](#updating-a-pull-request).\n2. Read the repository's `AGENTS.md` for its conventions, such as ticket references or required sections.\n3. Look for a pull request template, usually `.github\u002Fpull_request_template.md`. If there is one, fill it in: use its sections, in its order, instead of the structure below.\n4. Read the whole change against the branch it will merge into, for example with `git diff main...HEAD`, and read the commit messages.\n5. Find the reason for the change: the linked issue, the conversation that led to it, or the author's explanation. If you can't tell why the change was made, ask rather than invent a reason.\n\n## The title\n\nUse a [Conventional Commit](https:\u002F\u002Fwww.conventionalcommits.org\u002F) title, `type(scope): summary`, because many of our repositories squash-merge pull requests and the title becomes the commit on `main`. Write the summary in the imperative and lower case, without a full stop, such as `feat(search): add lesson filters`. Add `!` for a breaking change, and keep the title under about 72 characters. If the repository's `AGENTS.md` doesn't say whether titles include a ticket ID, ask the user rather than guessing from past titles.\n\n## The description\n\nCover these two things, in this order. [Writing the description](references\u002Fpr-description.md) explains each one, with an example.\n\n1. **What and why.** Two sentences, about 50 words: the problem or the old behaviour, then what the change does. For two or more separate changes, one line that sums them up, then a short bullet for each. Link the issue.\n2. **Testing instructions.** [Testing instructions](references\u002Ftesting-instructions.md) a reviewer can follow. If the change is user-facing, always include them, as explicit, plain-English steps QA can follow, each with what they should see.\n\nLeave out anything the diff, the ticket or CI already shows. Add test evidence only when CI can't show it, in one line with a link.\n\n## Rules\n\n- Only claim what's true. If something wasn't tested, say so.\n- Never include secrets, credentials, personal data or internal links that shouldn't be public. Many of our repositories are public.\n- Link tickets and issues. Never leave a bare ticket number.\n- If the template has a checklist, leave its items for the author to tick, and don't strike through any that could apply.\n- For screenshots, leave a placeholder for the author, or write \"N\u002FA\" with a reason of a few words. Give every image alt text that says what it shows.\n- Write in plain British English for someone who hasn't seen the work. Define anything a reviewer outside the team might not know.\n\n## Opening the pull request\n\nPushing and opening a pull request are visible to other people, so never do either without the user's approval.\n\n1. Run the repository's checks, such as formatting, linting, type checking and tests, using the commands in `AGENTS.md`. If one fails, stop, show its output and offer to fix it. Report which checks ran, and never say a check passed if it didn't run. If the branch changes after the checks ran, run them again before pushing.\n2. Show the user the title, the description, the branch it merges into, the current branch and the commits it contains. Revise them as the user asks, showing the whole updated version each time, until they clearly approve it. Silence or a vague reply isn't approval. Then ask whether to push and open it, and whether as a draft, and don't go on until they say yes.\n3. Push only the current branch: `git push -u origin HEAD`.\n4. Open the pull request with the GitHub CLI, passing the description from a file so the shell can't change it: `gh pr create --title \"\u003Ctitle>\" --body-file \u003Cfile>`. Add `--draft` if the user asked for one, and `--base \u003Cbranch>` if it doesn't merge into the default branch.\n5. Don't request reviewers or add assignees unless the user asks you to.\n6. Give the user the pull request's link.\n7. Offer to watch its CI checks. Only watch if the user says yes. Run `gh pr checks \u003Cnumber> --watch`, in the background if you can, so the user isn't blocked. When the checks finish, say which passed and which failed, and offer to investigate any failure. If they're still running after about 15 minutes, stop watching, say so, and offer to keep going.\n\nIf `gh` isn't installed or signed in, give the user the title and description to paste instead.\n\n## Updating a pull request\n\nWhen the change grows or its approach changes after review, update the title and description so they still describe what will merge. Show the user the new version and wait for their approval, as when opening one, then apply it with `gh pr edit --title \"\u003Ctitle>\" --body-file \u003Cfile>`.\n",{"name":5,"license":15,"metadata":24,"description":7},{"owner":25,"updated":26},"@oaknational\u002Fskills-maintainers","2026-10-27","main","aa4f22c3a1650bc207889cf83b762af943a0e08a","skills\u002Fcentral\u002Foak-pr-create",1,"https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills","https:\u002F\u002Fgithub.com\u002Foaknational","https:\u002F\u002Fwww.thenational.academy\u002F","Creating an openly licensed, fully resourced and AI-enabled curriculum for teachers and pupils as a not for profit and independent Arm's Length Body of UK Gov","2026-11-11 04:39:53",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add oaknational\u002Foak-agent-skills --skill oak-pr-create",{"tool":42,"command":43},"bunx","bunx skills add oaknational\u002Foak-agent-skills --skill oak-pr-create",{"tool":45,"command":46},"pnpm","pnpm dlx skills add oaknational\u002Foak-agent-skills --skill oak-pr-create","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcentral\u002Foak-pr-create\u002FSKILL.md",true,[50,56],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fpr-description.md","REFERENCE","参考文档",1588,"https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcentral\u002Foak-pr-create\u002Freferences\u002Fpr-description.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Ftesting-instructions.md",3168,"https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fcentral\u002Foak-pr-create\u002Freferences\u002Ftesting-instructions.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7EJD9XXYMZVYTDQNRJHH3ZM","owa-routing","Routing for the web application. Use when a test needs a bundle skill.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Frepos\u002Fowa\u002Fowa-routing\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7EJD6PTM1D7YJE47QP531MG","oc-tokens","Design tokens for the component library. Use when a test needs another bundle.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Frepos\u002Foc\u002Foc-tokens\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7EJD3SSF5KRDS2WVD3EZ5QK","oak-gamma","The gamma test skill. Use when a test needs gamma.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Fcentral\u002Foak-gamma\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7EJD0QWKB318A0XG98Z9ANJ","oak-beta","The beta test skill. Use when a test needs beta.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Fcentral\u002Foak-beta\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7EJCXV42PQNWG6VGWQHDHWB","oak-alpha","The alpha test skill. Use when a test needs alpha.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fpackage\u002Fskills\u002Fcentral\u002Foak-alpha\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7EJCW482706XRCJ5Q5636KT","oak-example","An example skill for tests. Use it when a test needs a valid skill.","https:\u002F\u002Fgithub.com\u002Foaknational\u002Foak-agent-skills\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcentral-repo\u002Fskills\u002Fcentral\u002Foak-example\u002FSKILL.md",[],[]]