agentsclimarketplace

Snap resolve

Skill sadiksaifi/skills/snap-resolve

SNAP — agent skills for smart models that ship real software.

Install
npx -y skills add sadiksaifi/skills --skill snap-resolve

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Resolve GitHub PR feedback and failing checks. Use when the user wants review comments addressed, CI failures fixed, reviewer replies posted, or addressed review threads resolved.

SKILL.md

2.3 KB, as published. Nobody here has run it

Invocation

Syntax: /skill:snap-resolve [auto]

Args

KeyValuesDefaultNotes
helpboolfalseshow usage
autoboolfalseskip checkpoint approval for clear [FIX], [EXPLAIN], and CI items; never auto-run Unsure

Resolve GitHub PR feedback and failing checks. One checkpoint before execution unless auto is provided.

Process

  1. Find the PR from current branch/session context, or ask for one.

  2. Gather full PR context: title/body, comments, reviews, review threads, replies, checks, failed logs, and linked issues/specs/PRDs recursively when they affect scope, acceptance, blockers, or intent. Use references/ci-checks.md for CI failure parsing.

  3. Classify each current item, accounting for prior replies, resolved threads, commits, and CI reruns:

    • [FIX]: requires code/docs/test change
    • [EXPLAIN]: reply only; no code-change promise
    • CI: failing check or log-derived failure
    • Already addressed: prior reply/fix/CI update shows the item was handled; skip unless it is still failing or explicitly reopened
    • Unsure: missing, conflicting, or inaccessible context

  4. Show one checkpoint with [FIX], [EXPLAIN], CI, Already addressed, and Unsure. Wait for approval unless auto is provided. Never auto-run Unsure.

  5. Execute approved fixes. Use references/tdd-cycle.md for substantive fixes and direct edits for trivial fixes. Add tests only for meaningful behavior affected by the fix; do not add unnecessary coverage-only tests. Verify locally with targeted tests/checks for touched code. Do not wait for GitHub CI to turn green. Commit each fix atomically.

  6. Reply using references/thread-resolution.md: use true review-thread inline replies when a thread endpoint exists; for top-level PR comments, post a quote-reply comment that quotes the relevant original feedback. Resolve addressed review threads only after replying. Push once, then report commits, local verification, replies, pending CI if any, and remaining unresolved items. Do not watch or wait for GitHub CI after pushing.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.