[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FC3HDJH3C177GET4K9K9D1":3,"skill-same:01M7FC3HDJH3C177GET4K9K9D1":58},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7FC3HDJH3C177GET4K9K9D1","merge-batch",null,"Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fdevops\u002Fskills\u002Fmerge-batch\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: merge-batch\ndescription: Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.\nallowed-tools: Bash, Read, Edit, Write, Grep, Glob, AskUserQuestion\n---\n\n> **This skill needs OmniRoute, which is installed separately.** From this skill's folder, run `python3 scripts\u002Fsfp_app.py status` to see whether it is installed and running. If it is not, run `python3 scripts\u002Fsfp_app.py install` to get the plan (it changes nothing), tell the user what it will do, and run it again with `--yes` only after they agree. `start` runs it when it is installed but stopped.\n\n# Merge batch: shared preparation, exact admission\n\nRead `..\u002F_shared\u002Fbase-green.md`, `..\u002F_shared\u002Fvalidation-gate.md` and\n`..\u002F_shared\u002Fmerge-gates.md`. Their current-candidate, authority, protected-surface\nand credit rules govern this workflow. Historical throughput, administrative\nmerge and blanket rebaseline exceptions are superseded by that protocol.\n\nBatching shares discovery and conflict diagnosis. It does not make a combined\nboard's PASS evidence valid for different intermediate squash candidates.\n\n## 1. Intake and authority\n\nResolve each selected PR's open\u002Fdraft state, current head\u002Fbase, target, contributor\nand write authority. Read the diff and current freeze state, and check active\nworktree ownership. Hold any item another session is working. A request to analyze\nor prepare a list is not authority to merge or close it.\n\nRun `scripts\u002Fquality\u002Fcheck-skill-contract.mjs` against the actual installed skills\nroot before admission. Missing or drifted modeled instructions mean HOLD; a\ntemplate-only check does not verify the installation being used.\n\nShow a 1–5 star table with rationale, overlaps and holds. Stars prioritize work;\nthey do not waive required checks or protected-surface approval. Ask the owner\nbefore acting on low-star items or dispatching rework not already authorized.\nFor a subsumed item, prove the current behavior and obtain the separate per-item\nclosure decision; preserve the original PR when its work is being used.\n\nCompletion: selected scope, target, ownership and permitted actions are explicit.\n\n## 2. Build the diagnostic board\n\nPin the approved live base and record the ordered PR heads. Use one owned branch\nand worktree under `.claude\u002Fworktrees\u002F`, with active hooks and dependencies\nmatching the candidate lockfile. Verify dependency identity instead of assuming a\ncopy from the shared checkout is current. Do not install over shared hard links.\n\nBoard the selected refs and verify each is an ancestor of the combined head.\nResolve overlaps without dropping sibling behavior or contributor attribution.\nKeep unrelated worktrees and the shared checkout untouched; never use git stash.\nParallel preparation needs authorized delegation and disjoint write ownership.\n\nCompletion: the board has a recorded base, ordered heads, final SHA\u002Ftree and a\nscoped diff that contains every intended change and reconciliation.\n\n## 3. Diagnose and repair\n\nRun the applicable static profile and focused tests with their actual collectors.\nKeep stdout\u002Fstderr, exits, signals, versions and identities. These are PARTIAL\nevidence, not merge acceptance. Full workflow evidence can be supplied by the\napproved server queue; it need not be redundantly simulated for every local probe.\n\nCompare a failed requirement on the exact pinned base under comparable runtime\nand installation before attributing it. Record resource\u002Fsetup interruptions\nseparately. Controlled repetitions may diagnose instability; a later PASS does\nnot erase an earlier required FAIL. Preserve assertions, thresholds and baselines.\n\nApply every required conflict, i18n, documentation and code reconciliation to\nthe candidate before its acceptance. Do not deliberately land a red tip and\npromise a follow-up after distributing the batch.\n\nCompletion: proven defects have scoped RED\u002FGREEN evidence, and remaining failures\nor incomplete lanes have explicit dispositions without green-by-bypass.\n\n## 4. Admit each actual landing\n\nUse the shared merge gates for every selected PR\u002Fgroup. Resolve its current base,\nhead, tested candidate and policy again. Require all applicable required lanes,\nincluding `Gate \u002F CI`, `Gate \u002F Quality` and requirements outside those aggregates.\nDraft skips, MERGEABLE, a green board, an old head and inherited failures are not\nacceptance. A changed identity returns the item to validation.\n\nUse an approved server-enforced queue or reviewed identity-preserving protocol\nfor each actual landing. `gh pr merge --match-head-commit` guards the head only;\nit does not atomically guard the base or replace missing required checks. If the\ntool cannot preserve the tested candidate or exclude a race, HOLD.\n\nMerge only the owner-authorized item after protected-surface approval where\napplicable. Keep contributor fixes in their authorized branch; a locked fork\nneeds the shared credit-preserving fallback, not a direct protected-branch push.\nAdministrative bypass, trust approval and release\u002Fdeploy authority are separate\nexceptional decisions, never inferred from a batch request or star rating.\n\nCompletion: the actual landed identity has current required evidence and the\nspecific authority for that mutation, or the item remains prepared\u002FHOLD.\n\n## 5. Readback and handoff\n\nVerify merged state, actual SHA\u002Ftree and contributor credit. Refresh and validate\nthe resulting base before admitting the next landing. Report prepared, integrated\nand currently validated separately; a partially landed batch is not a full PASS.\n\nRetain an ordered ledger of PRs, base\u002Fhead\u002Fcandidate\u002Flanding identities, checks,\nreceipts, contributor attribution and holds in the owned private task artifacts.\nClose only separately authorized items and use the shared credit rules. Preserve\nevidence before safe teardown of worktrees created for this batch; never remove\nanother session's work or leave the shared checkout on a different branch.\n","> **This skill needs OmniRoute, which is installed separately.** From this skill's folder, run `python3 scripts\u002Fsfp_app.py status` to see whether it is installed and running. If it is not, run `python3 scripts\u002Fsfp_app.py install` to get the plan (it changes nothing), tell the user what it will do, and run it again with `--yes` only after they agree. `start` runs it when it is installed but stopped.\n\n# Merge batch: shared preparation, exact admission\n\nRead `..\u002F_shared\u002Fbase-green.md`, `..\u002F_shared\u002Fvalidation-gate.md` and\n`..\u002F_shared\u002Fmerge-gates.md`. Their current-candidate, authority, protected-surface\nand credit rules govern this workflow. Historical throughput, administrative\nmerge and blanket rebaseline exceptions are superseded by that protocol.\n\nBatching shares discovery and conflict diagnosis. It does not make a combined\nboard's PASS evidence valid for different intermediate squash candidates.\n\n## 1. Intake and authority\n\nResolve each selected PR's open\u002Fdraft state, current head\u002Fbase, target, contributor\nand write authority. Read the diff and current freeze state, and check active\nworktree ownership. Hold any item another session is working. A request to analyze\nor prepare a list is not authority to merge or close it.\n\nRun `scripts\u002Fquality\u002Fcheck-skill-contract.mjs` against the actual installed skills\nroot before admission. Missing or drifted modeled instructions mean HOLD; a\ntemplate-only check does not verify the installation being used.\n\nShow a 1–5 star table with rationale, overlaps and holds. Stars prioritize work;\nthey do not waive required checks or protected-surface approval. Ask the owner\nbefore acting on low-star items or dispatching rework not already authorized.\nFor a subsumed item, prove the current behavior and obtain the separate per-item\nclosure decision; preserve the original PR when its work is being used.\n\nCompletion: selected scope, target, ownership and permitted actions are explicit.\n\n## 2. Build the diagnostic board\n\nPin the approved live base and record the ordered PR heads. Use one owned branch\nand worktree under `.claude\u002Fworktrees\u002F`, with active hooks and dependencies\nmatching the candidate lockfile. Verify dependency identity instead of assuming a\ncopy from the shared checkout is current. Do not install over shared hard links.\n\nBoard the selected refs and verify each is an ancestor of the combined head.\nResolve overlaps without dropping sibling behavior or contributor attribution.\nKeep unrelated worktrees and the shared checkout untouched; never use git stash.\nParallel preparation needs authorized delegation and disjoint write ownership.\n\nCompletion: the board has a recorded base, ordered heads, final SHA\u002Ftree and a\nscoped diff that contains every intended change and reconciliation.\n\n## 3. Diagnose and repair\n\nRun the applicable static profile and focused tests with their actual collectors.\nKeep stdout\u002Fstderr, exits, signals, versions and identities. These are PARTIAL\nevidence, not merge acceptance. Full workflow evidence can be supplied by the\napproved server queue; it need not be redundantly simulated for every local probe.\n\nCompare a failed requirement on the exact pinned base under comparable runtime\nand installation before attributing it. Record resource\u002Fsetup interruptions\nseparately. Controlled repetitions may diagnose instability; a later PASS does\nnot erase an earlier required FAIL. Preserve assertions, thresholds and baselines.\n\nApply every required conflict, i18n, documentation and code reconciliation to\nthe candidate before its acceptance. Do not deliberately land a red tip and\npromise a follow-up after distributing the batch.\n\nCompletion: proven defects have scoped RED\u002FGREEN evidence, and remaining failures\nor incomplete lanes have explicit dispositions without green-by-bypass.\n\n## 4. Admit each actual landing\n\nUse the shared merge gates for every selected PR\u002Fgroup. Resolve its current base,\nhead, tested candidate and policy again. Require all applicable required lanes,\nincluding `Gate \u002F CI`, `Gate \u002F Quality` and requirements outside those aggregates.\nDraft skips, MERGEABLE, a green board, an old head and inherited failures are not\nacceptance. A changed identity returns the item to validation.\n\nUse an approved server-enforced queue or reviewed identity-preserving protocol\nfor each actual landing. `gh pr merge --match-head-commit` guards the head only;\nit does not atomically guard the base or replace missing required checks. If the\ntool cannot preserve the tested candidate or exclude a race, HOLD.\n\nMerge only the owner-authorized item after protected-surface approval where\napplicable. Keep contributor fixes in their authorized branch; a locked fork\nneeds the shared credit-preserving fallback, not a direct protected-branch push.\nAdministrative bypass, trust approval and release\u002Fdeploy authority are separate\nexceptional decisions, never inferred from a batch request or star rating.\n\nCompletion: the actual landed identity has current required evidence and the\nspecific authority for that mutation, or the item remains prepared\u002FHOLD.\n\n## 5. Readback and handoff\n\nVerify merged state, actual SHA\u002Ftree and contributor credit. Refresh and validate\nthe resulting base before admitting the next landing. Report prepared, integrated\nand currently validated separately; a partially landed batch is not a full PASS.\n\nRetain an ordered ledger of PRs, base\u002Fhead\u002Fcandidate\u002Flanding identities, checks,\nreceipts, contributor attribution and holds in the owned private task artifacts.\nClose only separately authorized items and use the shared credit rules. Preserve\nevidence before safe teardown of worktrees created for this batch; never remove\nanother session's work or leave the shared checkout on a different branch.\n",{"name":5,"description":7,"allowed-tools":24},"Bash, Read, Edit, Write, Grep, Glob, AskUserQuestion","main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fdevops\u002Fskills\u002Fmerge-batch",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add siddu1004\u002FSFP --skill merge-batch",{"tool":40,"command":41},"bunx","bunx skills add siddu1004\u002FSFP --skill merge-batch",{"tool":43,"command":44},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill merge-batch","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fdevops\u002Fskills\u002Fmerge-batch\u002FSKILL.md",true,[48,54],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"scripts\u002Fapp.json","SCRIPT","脚本",1615,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fdevops\u002Fskills\u002Fmerge-batch\u002Fscripts\u002Fapp.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"scripts\u002Fsfp_app.py",10329,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fdevops\u002Fskills\u002Fmerge-batch\u002Fscripts\u002Fsfp_app.py",[59,66,73,80,87,94],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"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},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\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},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]