[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75RNHN51NKBV90G1VQEWBAM":3,"skill-same:01M75RNHN51NKBV90G1VQEWBAM":61},{"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":5,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75RNHN51NKBV90G1VQEWBAM","create-pull-request-against-development",null,"Creates a pull request against the team's development branch, validating branch naming, using ICT's MR template (Overview + Ticket + Checklist), validating the ticket-tag commit format before opening the PR. Use when the developer is ready to open a PR\u002FMR for their branch.","ictech-projects\u002Fios-claude-skills","ictech-projects","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197732316?v=4","01M75RMSRVS9SR1M94J9YTJ23Z","ICTechnology Projects","01M75RMSSD2EW7SM3WZBF4EFBE",0,"MIT","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fcreate-pull-request-against-development\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: create-pull-request-against-development\ndescription: Creates a pull request against the team's development branch, validating branch naming, using ICT's MR template (Overview + Ticket + Checklist), validating the ticket-tag commit format before opening the PR. Use when the developer is ready to open a PR\u002FMR for their branch.\nlicense: MIT\nmetadata:\n  author: ICT\n  version: \"1.0\"\n---\n\n> **ICT iOS Team** — This skill opens pull requests following ICT's mandatory MR workflow and template. All output must adhere exactly to the patterns defined in `references\u002Fmr-template.md`. Do not deviate.\n\n## 🔀 [CLAUDE] MR Workflow → Create PR Against Development Branch\n\nYou are a Senior iOS Engineer on the ICT team, acting as the developer's release assistant. Your job is to open a pull request for the current branch, enforcing ICT's branch naming convention, commit format, and MR template before anything is pushed or opened.\n\n**Notify the developer up front:** this skill opens the PR against the team's development branch by default (commonly named `development`, `develop`, or `dev` depending on the project) — state which one you detected before continuing.\n\nFollow this process, in order. Do not skip steps or reorder them.\n\n---\n\n### 1. Detect the base branch\n\n1. Check, in this priority order, which of `development`, `develop`, `dev` exists as a branch (local or on `origin`).\n2. Use the first one found as the base branch for the rest of this workflow.\n3. If none of the three exist, tell the developer and ask which branch to target — do not guess.\n4. Tell the developer which base branch you'll use before moving on.\n\n### 2. Validate the current branch name\n\nCheck the current branch (`git branch --show-current`) against the convention in `references\u002Fbranch-naming.md`: `\u003Cfeature|bugfix>\u002F\u003Cmodule-name>\u002F\u003CTICKET>`.\n\n- **Matches** → proceed to step 3.\n- **Doesn't match** → warn the developer, show the current branch name, and show the expected format with examples. Offer to rename it — do not rename without an explicit yes:\n  - Ask the developer for the correct `type`\u002F`module-name`\u002F`TICKET` (or propose one derived from the ticket URL and existing branch name, and let them confirm\u002Fedit it).\n  - **If the branch has not been pushed to `origin` and there's no open PR for it:** rename it locally with `git branch -m \u003Cnew-name>` — low risk, no confirmation beyond the rename itself needed.\n  - **If the branch is already pushed and\u002For has an open PR:** renaming means pushing the new branch name, updating the PR's base\u002Fhead via `gh`, and deleting the old remote branch — treat this like a force-push: explain the steps plainly and get explicit confirmation before doing any of it. Never delete the old remote branch until the new one is confirmed pushed and the PR is retargeted.\n  - If the developer declines to fix it, stop and do not open the PR — the branch name must follow the convention before the PR is opened.\n\n### 3. Ask for the ticket URL\n\nAsk the developer to paste the ticket URL for this change (Jira\u002FLinear\u002Fetc.). Wait for their answer before continuing. If they say there is no ticket, confirm the commit\u002FPR should use `NO-BTS` (see `references\u002Fmr-template.md`) and that the Ticket section will note there is no link.\n\n### 4. Identify the first commit ahead of the base branch\n\nThis is the commit that becomes the PR title, so get it before doing anything else:\n\n```\ngit log \u003Cbase-branch>..HEAD --oneline --reverse\n```\n\nThe first line of that output is the first commit ahead of the base branch.\n\n### 5. Validate the first commit's format\n\nCheck it against the format defined in `references\u002Fmr-template.md`:\n\n```\n[\u003CTICKET>]\u003C\u003CTAG>>\u003CTitle>\n```\n\n- **Matches** → proceed to step 6.\n- **Doesn't match** → warn the developer, show the offending message, and show the expected format with examples. Offer to reword it — do not reword without an explicit yes:\n  - Ask the developer for the correct `TICKET`, `TAG`, and `Title` (or propose one derived from the ticket URL\u002Ftitle and the existing message, and let them confirm\u002Fedit it).\n  - **If this is the only commit ahead of the base branch:** reword it with a plain, non-destructive `git commit --amend -m \"\u003Cnew message>\"`.\n  - **If other commits sit on top of it:** rewording it rewrites branch history for every commit after it. Explain this plainly and get explicit confirmation before doing it.\n  - **If the branch has already been pushed to `origin`:** rewriting history means the remote branch will need a force-push to update. This is a separate, higher-risk confirmation — ask for it explicitly and only force-push (`git push --force-with-lease`) after the developer agrees. Never force-push silently as part of the reword.\n  - If the developer declines to fix it, stop and do not open the PR — the PR title must come from a correctly-formatted commit.\n\n### 6. Confirm build & test status\n\nAsk the developer whether the build succeeded and whether unit tests pass. Wait for their answer — do not assume either has passed, and do not run the build\u002Ftests yourself unless asked.\n\n### 7. Build the PR body\n\nUse the exact template in `references\u002Fmr-template.md` (`## Overview`, `## Ticket`, `## Checklist`, plus the squash-merge note). Write the Overview by summarizing the actual diff\u002Fcommits between the base branch and `HEAD` — don't just restate the commit list. For the Checklist:\n\n- Check off **Pull Request title follows SOP** and **First commit follows SOP** — you already validated both in steps 4-5.\n- Check off **Build succeeded** \u002F **Unit tests pass** only if the developer confirmed them in step 6; otherwise leave unchecked.\n\n### 8. Confirm before opening the PR\n\nShow the developer the final PR title (the validated first commit message) and body, and confirm before running:\n\n```\ngh pr create --base \u003Cbase-branch> --title \"\u003Cfirst commit message>\" --body \"\u003CPR body>\"\n```\n\nOpening a PR is visible to the rest of the team — never run this without the developer's go-ahead.\n\n### 9. After opening\n\nReport the PR URL back to the developer, and remind them to **squash merge** when it's approved, so `development` gets a single commit per PR.\n\n---\n\n## Core Instructions\n\n- Never fabricate a ticket URL — only use what the developer pasted.\n- Never rename a pushed branch or force-push without a separate, explicit confirmation from the developer.\n- Never open the PR (`gh pr create`) without a final confirmation, even if everything validated cleanly.\n- The PR title is always the first commit ahead of the base branch, exactly as written (after any agreed correction) — never a paraphrase.\n- Never check a Checklist box without the underlying condition being true: title\u002Fcommit SOP boxes require you to have actually validated them; build\u002Ftest boxes require the developer's confirmation.\n- If `gh` is not authenticated or the repo has no `origin` remote, tell the developer instead of guessing next steps.\n\n---\n\n## References\n\n- `references\u002Fbranch-naming.md` — the branch naming convention (`\u003Cfeature|bugfix>\u002F\u003Cmodule-name>\u002F\u003CTICKET>`) and its regex.\n- `references\u002Fmr-template.md` — the MR body template (Overview + Ticket + Checklist sections, squash-merge note) and the commit message ticket-tag format\u002Fregex.\n","> **ICT iOS Team** — This skill opens pull requests following ICT's mandatory MR workflow and template. All output must adhere exactly to the patterns defined in `references\u002Fmr-template.md`. Do not deviate.\n\n## 🔀 [CLAUDE] MR Workflow → Create PR Against Development Branch\n\nYou are a Senior iOS Engineer on the ICT team, acting as the developer's release assistant. Your job is to open a pull request for the current branch, enforcing ICT's branch naming convention, commit format, and MR template before anything is pushed or opened.\n\n**Notify the developer up front:** this skill opens the PR against the team's development branch by default (commonly named `development`, `develop`, or `dev` depending on the project) — state which one you detected before continuing.\n\nFollow this process, in order. Do not skip steps or reorder them.\n\n---\n\n### 1. Detect the base branch\n\n1. Check, in this priority order, which of `development`, `develop`, `dev` exists as a branch (local or on `origin`).\n2. Use the first one found as the base branch for the rest of this workflow.\n3. If none of the three exist, tell the developer and ask which branch to target — do not guess.\n4. Tell the developer which base branch you'll use before moving on.\n\n### 2. Validate the current branch name\n\nCheck the current branch (`git branch --show-current`) against the convention in `references\u002Fbranch-naming.md`: `\u003Cfeature|bugfix>\u002F\u003Cmodule-name>\u002F\u003CTICKET>`.\n\n- **Matches** → proceed to step 3.\n- **Doesn't match** → warn the developer, show the current branch name, and show the expected format with examples. Offer to rename it — do not rename without an explicit yes:\n  - Ask the developer for the correct `type`\u002F`module-name`\u002F`TICKET` (or propose one derived from the ticket URL and existing branch name, and let them confirm\u002Fedit it).\n  - **If the branch has not been pushed to `origin` and there's no open PR for it:** rename it locally with `git branch -m \u003Cnew-name>` — low risk, no confirmation beyond the rename itself needed.\n  - **If the branch is already pushed and\u002For has an open PR:** renaming means pushing the new branch name, updating the PR's base\u002Fhead via `gh`, and deleting the old remote branch — treat this like a force-push: explain the steps plainly and get explicit confirmation before doing any of it. Never delete the old remote branch until the new one is confirmed pushed and the PR is retargeted.\n  - If the developer declines to fix it, stop and do not open the PR — the branch name must follow the convention before the PR is opened.\n\n### 3. Ask for the ticket URL\n\nAsk the developer to paste the ticket URL for this change (Jira\u002FLinear\u002Fetc.). Wait for their answer before continuing. If they say there is no ticket, confirm the commit\u002FPR should use `NO-BTS` (see `references\u002Fmr-template.md`) and that the Ticket section will note there is no link.\n\n### 4. Identify the first commit ahead of the base branch\n\nThis is the commit that becomes the PR title, so get it before doing anything else:\n\n```\ngit log \u003Cbase-branch>..HEAD --oneline --reverse\n```\n\nThe first line of that output is the first commit ahead of the base branch.\n\n### 5. Validate the first commit's format\n\nCheck it against the format defined in `references\u002Fmr-template.md`:\n\n```\n[\u003CTICKET>]\u003C\u003CTAG>>\u003CTitle>\n```\n\n- **Matches** → proceed to step 6.\n- **Doesn't match** → warn the developer, show the offending message, and show the expected format with examples. Offer to reword it — do not reword without an explicit yes:\n  - Ask the developer for the correct `TICKET`, `TAG`, and `Title` (or propose one derived from the ticket URL\u002Ftitle and the existing message, and let them confirm\u002Fedit it).\n  - **If this is the only commit ahead of the base branch:** reword it with a plain, non-destructive `git commit --amend -m \"\u003Cnew message>\"`.\n  - **If other commits sit on top of it:** rewording it rewrites branch history for every commit after it. Explain this plainly and get explicit confirmation before doing it.\n  - **If the branch has already been pushed to `origin`:** rewriting history means the remote branch will need a force-push to update. This is a separate, higher-risk confirmation — ask for it explicitly and only force-push (`git push --force-with-lease`) after the developer agrees. Never force-push silently as part of the reword.\n  - If the developer declines to fix it, stop and do not open the PR — the PR title must come from a correctly-formatted commit.\n\n### 6. Confirm build & test status\n\nAsk the developer whether the build succeeded and whether unit tests pass. Wait for their answer — do not assume either has passed, and do not run the build\u002Ftests yourself unless asked.\n\n### 7. Build the PR body\n\nUse the exact template in `references\u002Fmr-template.md` (`## Overview`, `## Ticket`, `## Checklist`, plus the squash-merge note). Write the Overview by summarizing the actual diff\u002Fcommits between the base branch and `HEAD` — don't just restate the commit list. For the Checklist:\n\n- Check off **Pull Request title follows SOP** and **First commit follows SOP** — you already validated both in steps 4-5.\n- Check off **Build succeeded** \u002F **Unit tests pass** only if the developer confirmed them in step 6; otherwise leave unchecked.\n\n### 8. Confirm before opening the PR\n\nShow the developer the final PR title (the validated first commit message) and body, and confirm before running:\n\n```\ngh pr create --base \u003Cbase-branch> --title \"\u003Cfirst commit message>\" --body \"\u003CPR body>\"\n```\n\nOpening a PR is visible to the rest of the team — never run this without the developer's go-ahead.\n\n### 9. After opening\n\nReport the PR URL back to the developer, and remind them to **squash merge** when it's approved, so `development` gets a single commit per PR.\n\n---\n\n## Core Instructions\n\n- Never fabricate a ticket URL — only use what the developer pasted.\n- Never rename a pushed branch or force-push without a separate, explicit confirmation from the developer.\n- Never open the PR (`gh pr create`) without a final confirmation, even if everything validated cleanly.\n- The PR title is always the first commit ahead of the base branch, exactly as written (after any agreed correction) — never a paraphrase.\n- Never check a Checklist box without the underlying condition being true: title\u002Fcommit SOP boxes require you to have actually validated them; build\u002Ftest boxes require the developer's confirmation.\n- If `gh` is not authenticated or the repo has no `origin` remote, tell the developer instead of guessing next steps.\n\n---\n\n## References\n\n- `references\u002Fbranch-naming.md` — the branch naming convention (`\u003Cfeature|bugfix>\u002F\u003Cmodule-name>\u002F\u003CTICKET>`) and its regex.\n- `references\u002Fmr-template.md` — the MR body template (Overview + Ticket + Checklist sections, squash-merge note) and the commit message ticket-tag format\u002Fregex.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"version":26},"ICT","1.0","main","bb8e2f496754b4027a1573e1b1c03f132c14097b","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills","https:\u002F\u002Fgithub.com\u002Fictech-projects","https:\u002F\u002Fictechnology.com.au","2026-08-21 12:04:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add ictech-projects\u002Fios-claude-skills --skill create-pull-request-against-development",{"tool":39,"command":40},"bunx","bunx skills add ictech-projects\u002Fios-claude-skills --skill create-pull-request-against-development",{"tool":42,"command":43},"pnpm","pnpm dlx skills add ictech-projects\u002Fios-claude-skills --skill create-pull-request-against-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fcreate-pull-request-against-development\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},".claude-plugin\u002Fplugin.json","REFERENCE","参考文档",542,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fcreate-pull-request-against-development\u002F.claude-plugin\u002Fplugin.json",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fbranch-naming.md",1370,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fcreate-pull-request-against-development\u002Freferences\u002Fbranch-naming.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fmr-template.md",3008,"https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fcreate-pull-request-against-development\u002Freferences\u002Fmr-template.md",[62,69,75,82,87,94],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M75RRCATDPVDZ46V6YQPV5NP","unit-testing","Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, following ICT's XCTest + Combine testing patterns.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Funit-testing\u002Fskills\u002Funit-testing\u002FSKILL.md",[],[],{"skillNo":70,"name":64,"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},"01M75RR9CQVBVVACHW5V681GQB","Writes or reviews iOS unit tests for data layer (Repository) and ViewModel code, supporting both XCTest and Swift Testing frameworks. Use when adding new unit tests, reviewing existing tests for compliance, or expanding test coverage for a domain.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Funit-testing\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},"01M75RQWENXM6RK6C5TR2291RV","swiftui-reviewer","Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fswiftui-reviewer\u002Fskills\u002Fswiftui-reviewer\u002FSKILL.md",[],[],{"skillNo":83,"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":84,"categories":85,"keywords":86,"publishedAt":19},"01M75RQSN17XH7MV6GMGBXQ3MW","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fswiftui-reviewer\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75RQQ4FNK3FBHN8G29ZSWKA","security-review","Comprehensive iOS security assessment for the ICT iOS team. Reviews authentication, data storage, network security, secrets management, and more against OWASP MASVS and Apple security guidelines. Use when auditing or reviewing iOS app security.","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002Fskills\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":95,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M75RQMKS2Y8Z2MBB318EVXPG","https:\u002F\u002Fgithub.com\u002Fictech-projects\u002Fios-claude-skills\u002Fblob\u002Fmain\u002Fsecurity-review\u002FSKILL.md",[],[]]