[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M757DRG3ASMDP0MWFZXQNCMY":3,"skill-same:01M757DRG3ASMDP0MWFZXQNCMY":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M757DRG3ASMDP0MWFZXQNCMY","pull-request",null,"Send a Github Pull Request of your work. Normally done after completing a ticket\u002Fissue. Check on CI and follow up on any failures.","gregwebs\u002Fskills-sdlc","gregwebs","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1183?v=4","01M757CE9SQ3192K1V45RCV63N","Greg Weber","01M757CEAEWMH9VKD0C4BH22BV",21,"MIT","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fpull-request\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: pull-request\ndescription: Send a Github Pull Request of your work. Normally done after completing a ticket\u002Fissue. Check on CI and follow up on any failures.\nmetadata:\n  short-description: Send a Github Pull Request and check on CI\n---\n\n## Definitions\n\nPR=Pull Request\n\n## Access\n\nAccess Github if the capability is available and the user instructs it.\n* skills\n  * \u002Fgithub-app skill: push with `${CLAUDE_SKILL_DIR}\u002F..\u002Fgithub-app\u002Fscripts\u002Fgh-app.sh git push`, then create the PR with `${CLAUDE_SKILL_DIR}\u002F..\u002Fgithub-app\u002Fscripts\u002Fgh-app.sh pr create`\n  * \u002Fgithub-actions-ci: check on CI with its bundled helper\n* Github API or MCP\n* github CLI \n\n## Branching\n\nUpdate the default branch to the latest from the origin.\nIf you were already on the default branch, branch from there.\nOtherwise, check if the current branch has been merged into the updated default (could be a squash merge).\nIf it has been merged, then branch off the updated default (move your changes there).\nOtherwise, branch off of the current branch. First ensure the updated default is merged into it.\n\nIf you are working on a sub issue of a parent issue, then look for an active parent branch to use as the base.\nAll sub issues that do not have dependencies should use the discovered default branch or the parent branch as their base branch.\n\nIf the issue requires an existing PR to be merged, then the base branch will be the branch for that PR.\nCreate it as a [Stacked PR](https:\u002F\u002Fgithub.github.com\u002Fgh-stack\u002Fintroduction\u002Foverview\u002F).\n\n## Description\n\nFor the PR description, use the `\u002Fdocument-changes` skill.\nIf the PR resolves an issue, ensure it is auto-closed by using the \"Resolves\" keyword: \"Resolves #10\".\n\nWhen you write a commit message, follow these 7 rules:\nRule 1: Separate the subject line from the body with a single blank line.\nRule 2: Limit the subject line to 50 characters (72 is the absolute hard limit).\nRule 3: Capitalize the first letter of the subject line.\nRule 4: Do not end the subject line with a period.\nRule 5: Use the imperative mood in the subject line (e.g., \"Fix bug,\" \"Add feature,\"\n        not \"Fixed\" or \"Adds\"). Test formula: It must complete the sentence: \"If applied,\n        this commit will [your subject line here]\".\nRule 6: Wrap the body text manually at 72 characters to prevent Git formatting issues.\nRule 7: Use the body to explain what and why vs. how. Assume the code explains the how;\n        the message must explain the context and reasoning.\n\n## Check on CI\n\nWhen CI access is available and the user requested PR follow-up, check the CI run for the PR.\nIf there are CI failures, investigate them and change the PR.\n\nIf the CI failures are not related to your work, suggest filing an issue or otherwise fixing them separately.\nIf they are related to your work, and the changes needed are not minor, fix them using the same workflow you used to write the code.\n\nIf CI is in progress and the branch has multiple commits, check if there are incomplete runs on older commits that can be canceled. Ask the user if you can cancel them unless you are already pre-authorized to cancel.\n\n## Cleaning up history\n\nBefore pushing the PR, squash merge commits into a useful history.\nOnce the PR is opened, additional commits should be added on so reviewers can see additional changes.\nIf additional commits added onto the PR are not useful for history\n* if it is best to squash merge the PR into a single commit, tell the user\n* otherwise offer to squash a subset of the commits together\n","## Definitions\n\nPR=Pull Request\n\n## Access\n\nAccess Github if the capability is available and the user instructs it.\n* skills\n  * \u002Fgithub-app skill: push with `${CLAUDE_SKILL_DIR}\u002F..\u002Fgithub-app\u002Fscripts\u002Fgh-app.sh git push`, then create the PR with `${CLAUDE_SKILL_DIR}\u002F..\u002Fgithub-app\u002Fscripts\u002Fgh-app.sh pr create`\n  * \u002Fgithub-actions-ci: check on CI with its bundled helper\n* Github API or MCP\n* github CLI \n\n## Branching\n\nUpdate the default branch to the latest from the origin.\nIf you were already on the default branch, branch from there.\nOtherwise, check if the current branch has been merged into the updated default (could be a squash merge).\nIf it has been merged, then branch off the updated default (move your changes there).\nOtherwise, branch off of the current branch. First ensure the updated default is merged into it.\n\nIf you are working on a sub issue of a parent issue, then look for an active parent branch to use as the base.\nAll sub issues that do not have dependencies should use the discovered default branch or the parent branch as their base branch.\n\nIf the issue requires an existing PR to be merged, then the base branch will be the branch for that PR.\nCreate it as a [Stacked PR](https:\u002F\u002Fgithub.github.com\u002Fgh-stack\u002Fintroduction\u002Foverview\u002F).\n\n## Description\n\nFor the PR description, use the `\u002Fdocument-changes` skill.\nIf the PR resolves an issue, ensure it is auto-closed by using the \"Resolves\" keyword: \"Resolves #10\".\n\nWhen you write a commit message, follow these 7 rules:\nRule 1: Separate the subject line from the body with a single blank line.\nRule 2: Limit the subject line to 50 characters (72 is the absolute hard limit).\nRule 3: Capitalize the first letter of the subject line.\nRule 4: Do not end the subject line with a period.\nRule 5: Use the imperative mood in the subject line (e.g., \"Fix bug,\" \"Add feature,\"\n        not \"Fixed\" or \"Adds\"). Test formula: It must complete the sentence: \"If applied,\n        this commit will [your subject line here]\".\nRule 6: Wrap the body text manually at 72 characters to prevent Git formatting issues.\nRule 7: Use the body to explain what and why vs. how. Assume the code explains the how;\n        the message must explain the context and reasoning.\n\n## Check on CI\n\nWhen CI access is available and the user requested PR follow-up, check the CI run for the PR.\nIf there are CI failures, investigate them and change the PR.\n\nIf the CI failures are not related to your work, suggest filing an issue or otherwise fixing them separately.\nIf they are related to your work, and the changes needed are not minor, fix them using the same workflow you used to write the code.\n\nIf CI is in progress and the branch has multiple commits, check if there are incomplete runs on older commits that can be canceled. Ask the user if you can cancel them unless you are already pre-authorized to cancel.\n\n## Cleaning up history\n\nBefore pushing the PR, squash merge commits into a useful history.\nOnce the PR is opened, additional commits should be added on so reviewers can see additional changes.\nIf additional commits added onto the PR are not useful for history\n* if it is best to squash merge the PR into a single commit, tell the user\n* otherwise offer to squash a subset of the commits together\n",{"name":5,"metadata":24,"description":7},{"short-description":25},"Send a Github Pull Request and check on CI","main","4107310104a727eddf4ff7564540a1d55a5e9422","skills\u002Fpull-request",1,"https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc","https:\u002F\u002Fgithub.com\u002Fgregwebs","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fgregabramowitzweber","2026-11-12 21:43:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add gregwebs\u002Fskills-sdlc --skill pull-request",{"tool":40,"command":41},"bunx","bunx skills add gregwebs\u002Fskills-sdlc --skill pull-request",{"tool":43,"command":44},"pnpm","pnpm dlx skills add gregwebs\u002Fskills-sdlc --skill pull-request","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fpull-request\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M78SFA6PHFHHTGWBDHJQBJHZ","easy-issues","Find and work through easy issue-tracker tasks autonomously, simplest first, using one fresh subagent per issue in sequence. Use for clearing straightforward bugs, documentation fixes, and tiny features without operator help.","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fexperimental\u002Feasy-issues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M757E63FW42JCM5ACS9A7APJ","wrap-up","After implementing, commit and finish your work","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fwrap-up\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M757E4D8DYA9QMRQMZNAA442","verify","Verify software by intentional testing.","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fverify\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M757E2T6F62NE29Q1XTN5EP8","update-working-copy","Fetch the latest from the remote. Update the working branch or switch to main if the branch is defunct.","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-working-copy\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M757E0PYSK3HW3WS9BPR5EEF","tickets","Break a plan, spec, or conversation into tracer-bullet issues for this repo, creating a parent tracking issue with sub-issues when publishing multiple tickets.","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Ftickets\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M757DZ6KRKPYTHXBHG3D3EXK","spec","Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002Fgregwebs\u002Fskills-sdlc\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[],[]]