[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77MZJHND7VXTPF66H9VCNPM":3,"skill-same:01M77MZJHND7VXTPF66H9VCNPM":52},{"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":31,"commitSha":32,"skillDirectory":33,"forksCount":14,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M77MZJHND7VXTPF66H9VCNPM","mergeable-please",null,"Drive a GitHub pull request toward mergeable. Run when asked to \"make a PR mergeable\", \"loop until the PR is ready\", \"fix the PR until CI\u002Fconflicts\u002Freviews pass\", or similar. Repeatedly runs `mergeable-please check`, resolves each reported blocker (conflicts, behind-base, failing\u002Fpending required CI, reviewer-loop goals), and loops until the tool reports satisfied.","sushichan044\u002Fmergeable-please","sushichan044","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71284054?v=4","01M6CD61CFDCQYW4XTQ1CF5200","Kentaro Suzuki","01M77MTW96E9P0ZVAHK9FXG8TJ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002Fskills\u002Fmergeable-please\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mergeable-please\ndescription: Drive a GitHub pull request toward mergeable. Run when asked to \"make a PR mergeable\", \"loop until the PR is ready\", \"fix the PR until CI\u002Fconflicts\u002Freviews pass\", or similar. Repeatedly runs `mergeable-please check`, resolves each reported blocker (conflicts, behind-base, failing\u002Fpending required CI, reviewer-loop goals), and loops until the tool reports satisfied.\nlicense: MIT\ncompatibility:\n  - claude\n  - codex\n  - agents\nallowed_tools:\n  - Bash\n  - Read\n---\n\n# mergeable-please\n\nLoop a GitHub pull request to merge-readiness. `mergeable-please` is a stateless,\nsingle-shot CLI: it diagnoses every merge condition the agent can act on and\ntells you the next action. **You** drive the loop by re-running it after each fix.\n\n## The loop\n\n1. Run `mergeable-please check` (add the PR number or URL if you are not on the\n   PR's branch, e.g. `mergeable-please check 42`).\n2. `check` prints a task list. The first line is the header\n   `status: satisfied|blocked · owner\u002Frepo#n \u003Curl>`; then one checkbox per merge\n   condition and reviewer. Each item may carry indented supplements: a status\n   line (e.g. `rally 3\u002F5 · goal approved`) and a `→ action` naming the next move\n   and, after `·`, the one `view`\u002F`request` subcommand for depth. Trailing `~`\n   lines are human-only notes. Read the exit code and header:\n   - exit `0` \u002F `status: satisfied` → **stop**. Every `- [x]` is done; only\n     human-gated `~` advisories (if any) remain.\n   - exit `1` \u002F `status: blocked` → the `- [ ]` items are outstanding. Work them\n     top-down, following each item's indented `→ action`, then go back to step 1.\n   - exit `2` → a usage\u002Fconfig\u002FAPI error. Read the message and fix the invocation\n     (do not loop on this).\n3. For depth on any item, run the subcommand from its `→ action` (e.g.\n   `mergeable-please view --condition checks|conflicts|rules|reviewers`) — `check`\n   itself stays terse. Resolve each outstanding `- [ ]` item by its kind, then go\n   back to step 1:\n   - `conflict` → merge or rebase the base branch, resolve conflicts, commit, push.\n   - `behind-base` → the repo enforces up-to-date branches. Rebase onto the base\n     and push (`git fetch && git rebase origin\u002F\u003Cbase> && git push --force-with-lease`).\n   - `check-failing` → run `mergeable-please view --condition checks` to see which\n     required checks failed, investigate the root cause, fix it, push.\n   - `check-pending` → required checks are still running. Wait, then re-run check.\n   - `merge-eligibility-pending` → GitHub is still computing the merge state. Wait\n     15–30 seconds and re-run check.\n   - reviewer `N unresolved` → resolve those conversations first\n     (`mergeable-please view --condition reviewers` shows them), push, then\n     (re)request with `mergeable-please request --reviewer \u003Ctype:name>`.\n     Re-requests are blocked until the head advances, so always push your fix\n     first. After (re)requesting, the reviewer needs time to respond — poll in a\n     **background** shell (e.g. run `sleep 60 && mergeable-please check` as a\n     background job, never in the foreground) so you are not blocked.\n   - reviewer `changes requested` → the reviewer formally requested changes. Read\n     the review body and any threads (`view --condition reviewers`), address the\n     feedback, push, then re-request. If you genuinely cannot address the request\n     (e.g. it asks for a change you should not make) and no new commit is\n     possible, **stop and escalate to the human** — the tool will keep reporting\n     blocked, which is correct, and you must not loop. The item's `→ action` says\n     exactly this when it applies.\n   - reviewer `awaiting review` → no outstanding request; (re)request and poll in\n     the background as above.\n4. The trailing `~` lines are NOT blockers and never prevent `satisfied`:\n   - `~ approval required (human)` \u002F `~ ruleset block …` → require a human or\n     out-of-scope action. Report them as remaining follow-ups; do not try to\n     satisfy them yourself.\n   - `~ review notes present …` → a reviewer left a review body that may contain\n     findings not tied to any inline thread (e.g. CodeRabbit \"outside diff range\"\n     comments). Read it with `mergeable-please view --condition reviewers`.\n   - `~ … exhausted …` → a reviewer used all its rallies without meeting its\n     goal; stop the loop for it or raise `max-rallies`.\n\n## Notes\n\n- Prefer the exit code as the stop signal; the `status:` line is the human\u002Fagent\n  mirror of it.\n- Reviewer quality loops are opt-in via `.mergeable-please.yml` at the repo root.\n  With no config file, `check` evaluates conflicts and ruleset\u002FCI only.\n- After pushing a fix, give CI a moment before re-running `check`.\n","# mergeable-please\n\nLoop a GitHub pull request to merge-readiness. `mergeable-please` is a stateless,\nsingle-shot CLI: it diagnoses every merge condition the agent can act on and\ntells you the next action. **You** drive the loop by re-running it after each fix.\n\n## The loop\n\n1. Run `mergeable-please check` (add the PR number or URL if you are not on the\n   PR's branch, e.g. `mergeable-please check 42`).\n2. `check` prints a task list. The first line is the header\n   `status: satisfied|blocked · owner\u002Frepo#n \u003Curl>`; then one checkbox per merge\n   condition and reviewer. Each item may carry indented supplements: a status\n   line (e.g. `rally 3\u002F5 · goal approved`) and a `→ action` naming the next move\n   and, after `·`, the one `view`\u002F`request` subcommand for depth. Trailing `~`\n   lines are human-only notes. Read the exit code and header:\n   - exit `0` \u002F `status: satisfied` → **stop**. Every `- [x]` is done; only\n     human-gated `~` advisories (if any) remain.\n   - exit `1` \u002F `status: blocked` → the `- [ ]` items are outstanding. Work them\n     top-down, following each item's indented `→ action`, then go back to step 1.\n   - exit `2` → a usage\u002Fconfig\u002FAPI error. Read the message and fix the invocation\n     (do not loop on this).\n3. For depth on any item, run the subcommand from its `→ action` (e.g.\n   `mergeable-please view --condition checks|conflicts|rules|reviewers`) — `check`\n   itself stays terse. Resolve each outstanding `- [ ]` item by its kind, then go\n   back to step 1:\n   - `conflict` → merge or rebase the base branch, resolve conflicts, commit, push.\n   - `behind-base` → the repo enforces up-to-date branches. Rebase onto the base\n     and push (`git fetch && git rebase origin\u002F\u003Cbase> && git push --force-with-lease`).\n   - `check-failing` → run `mergeable-please view --condition checks` to see which\n     required checks failed, investigate the root cause, fix it, push.\n   - `check-pending` → required checks are still running. Wait, then re-run check.\n   - `merge-eligibility-pending` → GitHub is still computing the merge state. Wait\n     15–30 seconds and re-run check.\n   - reviewer `N unresolved` → resolve those conversations first\n     (`mergeable-please view --condition reviewers` shows them), push, then\n     (re)request with `mergeable-please request --reviewer \u003Ctype:name>`.\n     Re-requests are blocked until the head advances, so always push your fix\n     first. After (re)requesting, the reviewer needs time to respond — poll in a\n     **background** shell (e.g. run `sleep 60 && mergeable-please check` as a\n     background job, never in the foreground) so you are not blocked.\n   - reviewer `changes requested` → the reviewer formally requested changes. Read\n     the review body and any threads (`view --condition reviewers`), address the\n     feedback, push, then re-request. If you genuinely cannot address the request\n     (e.g. it asks for a change you should not make) and no new commit is\n     possible, **stop and escalate to the human** — the tool will keep reporting\n     blocked, which is correct, and you must not loop. The item's `→ action` says\n     exactly this when it applies.\n   - reviewer `awaiting review` → no outstanding request; (re)request and poll in\n     the background as above.\n4. The trailing `~` lines are NOT blockers and never prevent `satisfied`:\n   - `~ approval required (human)` \u002F `~ ruleset block …` → require a human or\n     out-of-scope action. Report them as remaining follow-ups; do not try to\n     satisfy them yourself.\n   - `~ review notes present …` → a reviewer left a review body that may contain\n     findings not tied to any inline thread (e.g. CodeRabbit \"outside diff range\"\n     comments). Read it with `mergeable-please view --condition reviewers`.\n   - `~ … exhausted …` → a reviewer used all its rallies without meeting its\n     goal; stop the loop for it or raise `max-rallies`.\n\n## Notes\n\n- Prefer the exit code as the stop signal; the `status:` line is the human\u002Fagent\n  mirror of it.\n- Reviewer quality loops are opt-in via `.mergeable-please.yml` at the repo root.\n  With no config file, `check` evaluates conflicts and ruleset\u002FCI only.\n- After pushing a fix, give CI a moment before re-running `check`.\n",{"name":5,"license":15,"description":7,"allowed_tools":24,"compatibility":27},[25,26],"Bash","Read",[28,29,30],"claude","codex","agents","main","31f700aa9c9e5d7b2fd01b0e5317d543b5321edd","skills\u002Fmergeable-please","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please","https:\u002F\u002Fgithub.com\u002Fsushichan044","A software engineer with a passion for novels and music.","2026-07-27 19:13:11",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add sushichan044\u002Fmergeable-please --skill mergeable-please",{"tool":44,"command":45},"bunx","bunx skills add sushichan044\u002Fmergeable-please --skill mergeable-please",{"tool":47,"command":48},"pnpm","pnpm dlx skills add sushichan044\u002Fmergeable-please --skill mergeable-please","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002Fskills\u002Fmergeable-please\u002FSKILL.md",true,[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M77MY6QVZ5GZE04ZBSSJARQ3","golang-troubleshooting","Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve debugger, race detection, GODEBUG tracing, and production debugging. Start here for any 'something is wrong' situation. Not for interpreting profiles or benchmarking (→ See `samber\u002Fcc-skills-golang@golang-benchmark` skill) or applying optimization patterns (→ See `samber\u002Fcc-skills-golang@golang-performance` skill).","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgolang-troubleshooting\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M77MXZ5D1S2951R8HJFCTWJG","golang-testing","Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI, or debugging flaky\u002Fslow tests. For testify-specific APIs see `samber\u002Fcc-skills-golang@golang-stretchr-testify`; for measurement methodology see `samber\u002Fcc-skills-golang@golang-benchmark`.","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgolang-testing\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M77MXPRC35GB96PS0BHN15BN","golang-structs-interfaces","Golang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfaces, struct field tags, and pointer vs value receivers. Use this skill when designing Go types, defining or implementing interfaces, embedding structs or interfaces, writing type assertions or type switches, adding struct field tags for JSON\u002FYAML\u002FDB serialization, or choosing between pointer and value receivers. Also use when the user asks about \"accept interfaces, return structs\", compile-time interface checks, or composing small interfaces into larger ones.","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgolang-structs-interfaces\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M77MXGQQ0VAA0N0V4HFPM8FV","golang-stretchr-testify","Comprehensive guide to stretchr\u002Ftestify for Golang testing. Covers assert, require, mock, and suite packages in depth. Use when writing tests with testify, creating mocks, setting up test suites, or choosing between assert and require. Covers testify assertions, mock expectations, argument matchers, call verification, suite lifecycle, and advanced patterns like Eventually, JSONEq, and custom matchers. Apply when the codebase imports github.com\u002Fstretchr\u002Ftestify.","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgolang-stretchr-testify\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M77MXA0301S3ZMGNQFA1XYPQ","golang-spf13-cobra","Golang CLI command tree library using spf13\u002Fcobra — cobra.Command, RunE vs Run, PersistentPreRunE hook chain, Args validators (NoArgs, ExactArgs, MatchAll, custom), persistent vs local flags, command groups, ValidArgsFunction, RegisterFlagCompletionFunc, ShellCompDirective, usage\u002Fhelp template customization, man-page and markdown doc generation, and testing with SetArgs\u002FSetOut\u002FSetErr. Apply when using or adopting spf13\u002Fcobra, or when the codebase imports `github.com\u002Fspf13\u002Fcobra`. For configuration layering alongside cobra, see the `samber\u002Fcc-skills-golang@golang-spf13-viper` skill. For general CLI architecture (project layout, exit codes, signal handling, I\u002FO patterns), see `samber\u002Fcc-skills-golang@golang-cli`.","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgolang-spf13-cobra\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M77MX4TDZA2XSE16PMJ1QZ74","golang-security","Security best practices and vulnerability prevention for Golang. Covers injection (SQL, command, XSS), cryptography, filesystem safety, network security, cookies, secrets management, memory safety, and logging. Apply when writing, reviewing, or auditing Go code for security, or when working on any risky code involving crypto, I\u002FO, secrets management, user input handling, or authentication. Includes configuration of security tools.","https:\u002F\u002Fgithub.com\u002Fsushichan044\u002Fmergeable-please\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgolang-security\u002FSKILL.md",[],[]]