[{"_1":2,"_281":-5,"_282":-5},"loaderData",{"_3":4,"_8":9,"_23":24},"root",{"_5":-5,"_6":7},"user","countable",true,"routes/_main",{"_5":-5,"_10":11},"recentPosts",[12,17,20],{"_13":14,"_15":16},"slug","best-mcp-servers-for-developers","title","The Best MCP Servers for Developers in 2026",{"_13":18,"_15":19},"claude-skill-and-plugin-security-scanning","Claude's Beta Skill and Plugin Security Scanning, Explained",{"_13":21,"_15":22},"mcp-tasks-extension-explained","How MCP's Tasks Extension Works","routes/creators.$handle",{"_25":26,"_27":26,"_28":29,"_30":31,"_32":33,"_279":31,"_280":111},"handle","martian-engineering","displayName","profileUrl","https://github.com/martian-engineering","verified",false,"skills",[34],{"_35":36,"_13":37,"_38":39,"_40":41,"_42":43,"_44":45,"_46":47,"_48":49,"_50":51,"_52":53,"_54":55,"_61":62,"_63":64,"_65":66,"_81":82,"_83":-5,"_84":85,"_86":87,"_88":89,"_90":91,"_92":93,"_94":-5,"_95":96,"_97":26,"_30":31,"_98":31,"_99":87,"_100":101,"_102":87,"_103":87,"_104":105,"_106":107,"_136":137,"_172":173,"_223":224,"_251":252,"_263":264,"_275":276,"_277":278},"id","gh__martian-engineering__lossless-claw__agents-skills-land-pr","lossless-pr-landing-martian-engineering","name","Lossless PR Landing","canonicalName","land-pr","tagline","Safely manage lossless-claw pull requests with confidence.","description","Land lossless-claw pull requests safely; use when asked whether a PR is ready, whether CI passes, to merge or land a PR, or to perform maintainer closeout after review.","longDescription","Lossless PR Landing is a specialized skill designed for developers who need to handle pull requests within the lossless-claw repository effectively. This skill guides users through the entire process of landing a pull request, ensuring that all necessary checks and balances are in place to maintain the integrity of the codebase. It emphasizes the importance of following repository-specific instructions and adheres to best practices for data preservation and compatibility.\n\nThe workflow begins with a thorough review of the repository's guidelines, particularly the AGENTS.md file, which outlines critical rules regarding changesets, command reporting, and more. The skill then assists in identifying the pull request head, fetching essential metadata to ensure that the correct version is being worked on. Users are prompted to verify the readiness of the pull request, checking for mergeability and successful completion of all required CI checks before proceeding.\n\nOnce the pull request is confirmed as ready, the skill facilitates a final review process, ensuring that all findings are addressed before merging. This includes searching for related open issues and ensuring that no unresolved actionable findings exist. The merging process itself is designed to be deterministic, with clear instructions on how to merge safely while preserving the commit history. After merging, the skill guides users through post-merge verification steps and encourages proper communication with contributors.\n\nLossless PR Landing is ideal for maintainers and contributors within the lossless-claw project who want to ensure that their pull requests are handled with care and precision. By following the structured approach provided by this skill, users can avoid common pitfalls associated with merging, such as overlooking critical checks or failing to address related issues.","primaryCategory","development","subcategory","code-review","secondaryCategories",[],"tags",[56,57,58,59,60],"lossless-claw","pull-request","merge","ci-checks","repository-management","skillType","workflow","complexity","intermediate","platforms",[67,68,69,70,71,72,73,74,75,76,77,78,79,80],"claude-code","claude-api","codex-cli","cursor","antigravity","github-copilot","windsurf","opencode","cline","roo-code","goose","kiro","continue","trae","delivery","source-link","skillFileUrl","pricing","free","price",0,"thumbnailType","icon","thumbnailIcon","git-branch","thumbnailColor","blue","thumbnailImageUrl","sellerId","gh__martian-engineering","sellerName","featured","downloads","views",2,"rating","reviewCount","status","active","metrics",{"_108":109,"_110":111,"_112":101,"_113":114,"_115":87,"_116":117,"_118":119,"_120":121,"_122":123,"_124":125,"_126":127,"_128":129,"_130":131,"_132":133,"_134":135},"freshnessScore",100,"mirrorCount",1,"skillCountInRepo","qualityScore",85,"daysSinceUpdate","popularityScore",75,"trustScore",65,"repoOpenIssues",216,"repoStars",4883,"repoWatchers",23,"repoContributors",89,"overallScore",81,"repoCreatedAt","2026-02-18T23:36:36Z","repoForks",440,"repoPushedAt","2026-08-11T00:14:26Z","source",{"_138":26,"_139":140,"_141":142,"_147":148,"_149":56,"_150":-5,"_145":151,"_152":153,"_154":148,"_155":31,"_156":157,"_158":159,"_165":166,"_167":7,"_168":169,"_170":171},"owner","repoUrl","https://github.com/martian-engineering/lossless-claw","author",{"_28":29,"_143":144,"_38":26,"_25":26,"_145":146},"avatarUrl","https://github.com/martian-engineering.png","type","User","lastSyncedAt","2026-08-11T01:34:04.172Z","repo","commitSha","github","branch","main","firstSeenAt","isOfficial","path",".agents/skills/land-pr","license",{"_38":160,"_161":162,"_163":164},"MIT License","spdxId","MIT","url","https://github.com/martian-engineering/lossless-claw/blob/main/LICENSE","sourceUpdatedAt","2026-08-10T23:56:40.000Z","redistributable","permalink","https://github.com/martian-engineering/lossless-claw/blob/main/.agents/skills/land-pr/SKILL.md","repoFullName","martian-engineering/lossless-claw","seo",{"_174":175,"_186":187,"_188":189,"_207":-5,"_208":209,"_215":216,"_217":218,"_219":220,"_221":222},"useCases",[176,180,183],{"_15":177,"_178":179},"Merging a Pull Request","body","Use this skill to safely merge a pull request after verifying all checks and ensuring no unresolved issues remain.",{"_15":181,"_178":182},"Final Review Process","Leverage this skill to conduct a thorough final review of a pull request before merging, ensuring compliance with repository standards.",{"_15":184,"_178":185},"Post-Merge Actions","Utilize this skill to perform necessary post-merge actions, such as closing related issues and thanking contributors.","whenNotToUse","This skill is not suitable for repositories outside of lossless-claw or for scenarios where pull requests do not require strict adherence to specific merging protocols.","faqs",[190,195,198,201,204],{"_191":192,"_193":194},"q","What is the purpose of this skill?","a","This skill helps users safely land pull requests in the lossless-claw repository by providing a structured workflow that ensures all checks are met.",{"_191":196,"_193":197},"How does the skill verify pull request readiness?","It checks if the pull request is open, non-draft, mergeable, and that all required CI checks have passed before allowing a merge.",{"_191":199,"_193":200},"Can I use this skill for other repositories?","No, this skill is specifically designed for the lossless-claw repository and follows its unique guidelines and processes.",{"_191":202,"_193":203},"What should I do if a pull request has unresolved issues?","You should not merge the pull request if there are unresolved actionable findings. Instead, address those findings before proceeding.",{"_191":205,"_193":206},"Is there a fallback method for merging if the preferred wrapper is unavailable?","Yes, the skill provides a manual fallback method for merging if the preferred wrapper is not present.","ogImageUrl","keywords",[210,211,212,213,214],"lossless-claw pull request","merge pull request safely","verify pull request readiness","CI checks for PR","repository merging guidelines","whenToUse","Use this skill whenever you need to land a pull request in the lossless-claw project, especially when verifying its readiness and compliance with repository standards.","metaTitle","Lossless PR Landing Skill for Safe Merging","problemSolved","This skill removes the uncertainty and risks associated with merging pull requests in the lossless-claw repository.","metaDescription","Manage lossless-claw pull requests safely and verify readiness with this structured skill. Click to learn more!","content",{"_225":87,"_226":227,"_235":236,"_245":246,"_247":31,"_248":249,"_250":231},"bundledFiles","fileTree",[228],{"_156":229,"_230":231,"_145":232,"_233":234},"SKILL.md","size",5067,"file","language","markdown","codeExamples",[237,241,243],{"_233":238,"_239":240},"bash","snippet","gh pr view --json number,title,state,isDraft,baseRefName,headRefName,headRefOid,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,author,files,closingIssuesReferences,url",{"_233":238,"_239":242},"gh pr checks --json name,state,bucket,workflow,link,startedAt,completedAt",{"_233":238,"_239":244},"head=$(gh pr view --json headRefOid --jq .headRefOid)\n base=$(gh pr view --json baseRefName --jq .baseRefName)\n gh pr checkout \n test \"$(git rev-parse HEAD)\" = \"$head\"\n /Users/phaedrus/Projects/prompts/skills/autoreview/scripts/autoreview --mode branch --base \"origin/$base\"","skillMd","# Lossless PR Landing\n\nUse this skill when landing a `lossless-claw` pull request or answering whether it is ready to merge.\n\n## Workflow\n\n1. Read repository instructions first.\n - Follow `AGENTS.md`, especially data-preservation, changeset, compatibility, and command-reporting rules.\n - If a deterministic merge wrapper exists for this repo, prefer it. Otherwise use the manual fallback below.\n\n2. Identify and pin the PR head.\n - Fetch the real PR metadata:\n ```bash\n gh pr view --json number,title,state,isDraft,baseRefName,headRefName,headRefOid,mergeable,mergeStateStatus,reviewDecision,statusCheckRollup,author,files,closingIssuesReferences,url\n ```\n - Treat `headRefOid` as the merge pin. Re-read it immediately before merge.\n\n3. Verify readiness.\n - PR must be open, non-draft, mergeable, and clean.\n - All required/current checks must be complete and successful on the pinned head:\n ```bash\n gh pr checks --json name,state,bucket,workflow,link,startedAt,completedAt\n ```\n - If checks are pending, failing, missing, or tied to a different head SHA, do not merge.\n - If the PR changes package-visible behavior, user-facing behavior, docs-visible behavior, compatibility metadata, config surface, or release behavior, answer the changeset question before merge.\n - Do not expect external contributors to add Changesets metadata. Maintainers own it.\n\n4. Run or confirm final review.\n - Prefer the repo's actual PR base:\n ```bash\n head=$(gh pr view --json headRefOid --jq .headRefOid)\n base=$(gh pr view --json baseRefName --jq .baseRefName)\n gh pr checkout \n test \"$(git rev-parse HEAD)\" = \"$head\"\n /Users/phaedrus/Projects/prompts/skills/autoreview/scripts/autoreview --mode branch --base \"origin/$base\"\n ```\n - Run branch review only from a checkout whose `HEAD` exactly matches the pinned PR `headRefOid`.\n - Verify every accepted finding against the code before acting on it.\n - Do not merge with unresolved actionable findings.\n\n5. Search open issues before merge closeout.\n - Inspect explicit closing references:\n ```bash\n gh pr view --json closingIssuesReferences --jq '.closingIssuesReferences'\n ```\n - Search open issues for likely duplicates or covered reports using the PR title, key error strings, feature names, changed behavior, and issue numbers mentioned in commits/body:\n ```bash\n gh issue list --state open --limit 50 --search \" repo:Martian-Engineering/lossless-claw\"\n ```\n - Read candidate issues before deciding they are covered:\n ```bash\n gh issue view --json number,title,state,body,url,labels,comments\n ```\n - If an issue is clearly fixed by the PR and not auto-closed by GitHub, close it after merge with a concise comment linking the merged PR.\n - If unsure, leave a comment on the issue noting the PR may help and ask for confirmation instead of closing.\n\n6. Merge deterministically.\n - Preferred wrapper, if present:\n ```bash\n scripts/pr-merge verify \n scripts/pr-merge run \n ```\n - Manual fallback:\n ```bash\n head=$(gh pr view --json headRefOid --jq .headRefOid)\n title=$(gh pr view --json title --jq .title)\n gh pr merge --squash --match-head-commit \"$head\" --subject \"$title\"\n ```\n - Never use `--auto` for this workflow.\n - Do not merge if the head SHA changed between verification and merge.\n\n7. Post-merge verification and maintainer follow-through.\n - Confirm the PR is `MERGED` and capture the merge commit:\n ```bash\n gh pr view --json state,mergeCommit,mergedAt,mergedBy,url\n ```\n - Leave a brief thank-you comment for external contributors after merge:\n ```bash\n gh pr comment --body \"Thanks for the contribution, @. This is landed now.\"\n ```\n - Close any verified covered issues that remain open, with a comment linking the PR and merge.\n - If a required changeset was not included before merge, immediately create a small follow-up PR that adds only the missing `.changeset/*.md`.\n\n8. Final report.\n - State whether the PR was ready and whether it was merged.\n - Include PR number/title, pinned head SHA, check summary, review command/result, merge command, merge commit SHA, contributor thank-you comment URL, issue-search outcome, closed/commented issues, and changeset outcome.\n - Include the commands run and their results in a code block, per `AGENTS.md`.\n\n## Do Not\n\n- Do not delete, purge, truncate, or otherwise discard persisted user data as part of landing.\n- Do not bypass failing or pending required checks.\n- Do not merge without head-SHA pinning.\n- Do not assume no related issues exist just because the PR body lacks `Fixes #...`.\n- Do not close ambiguous issues. Comment or report uncertainty instead.","skillMdTruncated","frontmatter",{"_38":41,"_44":45},"totalSizeBytes","runtime",{"_253":7,"_254":31,"_255":-5,"_256":31,"_257":31,"_258":31,"_259":260,"_261":262},"requiresBash","requiresMcp","model","requiresNode","requiresNetwork","requiresPython","allowedTools",[],"dependencies",[],"install",{"_265":266,"_267":268,"_269":270,"_271":272,"_273":274},"cli","npx skills add martian-engineering/lossless-claw/land-pr","coordinate","martian-engineering/lossless-claw/land-pr","browseUrl","https://github.com/martian-engineering/lossless-claw/tree/main/.agents/skills/land-pr","downloadUrl","https://github.com/martian-engineering/lossless-claw/archive/refs/heads/main.zip","gitUrl","https://github.com/martian-engineering/lossless-claw.git","createdAt","2026-08-11T01:34:08.216Z","updatedAt","2026-08-21T09:36:16.316Z","hasNext","page","actionData","errors"]