agentleFS
mampfesmampfes/hacs_waste_collection_schedule/.agents/skills/review-pr/SKILL.md

review-pr

Skill2.3k starsChanged 4 months agoLicence not identifiedView on GitHub

Review a pull request for hacs_waste_collection_schedule and execute only approved fixes or review actions. Use when the user asks to inspect, fix, approve, or request changes on a PR.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 0 mentionsApr 2026: 5 mentionsMay 2026: 4 mentionsJun 2026: 4 mentionsJul 2026: 4 mentionsAug 2026: 2 mentionsSep 2026: 6 mentionsOct 2026: 6 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the mampfes/hacs_waste_collection_schedule repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about mampfes/hacs_waste_collection_schedule

The biggest 5 of 53 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 53

Talked about on GitHub and Bluesky (53 times).

On GitHub · 50

45 more on GitHub
  • Other versions185 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 185

    1. denoland/deno★ 109ksame name
    2. ToolJet/ToolJet★ 41ksame name
    3. remix-run/remix★ 33ksame name
    4. tirth8205/code-review-graph★ 32ksame name
    5. alpinejs/alpine★ 32ksame name
    6. nrwl/nx★ 29ksame name
    7. jlowin/fastmcp★ 28ksame name
    8. PrefectHQ/fastmcp★ 28ksame name
    9. livewire/livewire★ 24ksame name
    10. microsoft/fluentui★ 20ksame name

    175 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use diagnose-ci-failures, review-delta and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • zerx-labSkill

      diagnose-ci-failures

      Diagnose CI failures for a PR using the GitHub CLI, extract error logs, and generate a plan to fix them. Use when the user asks to check CI status, pull CI issues, triage test failures, or investigate PR build failures.

      Also in 3 projects that use this

    • n24q02mSkill

      review-delta

      Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

      Also in 3 projects that use this

    • n24q02mSkill

      build-graph

      Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.

      Also in 3 projects that use this

    • zerx-labSkill

      write-product-spec

      Write a PRODUCT.md spec for a significant user-facing feature in Zap, focused on detailed behavior and validation. Use when the user asks for a product spec, desired behavior doc, or PRD, wants to define feature behavior before implementation, or when the feature is substantial or behaviorally ambiguous enough that a written spec would improve implementation or review.

      Also in 3 projects that use this

    • pooyakhosraviSkill

      add-dataset

      Add a new public ophthalmic or eye-related dataset to EyeDataHub end to end. Triggers when a user says "add a dataset", "register dataset X", "/add-dataset", or describes a new ophthalmic dataset they want indexed. Walks through source verification, DatasetInfo metadata, loader/backend implementation, registry registration, generated docs, tests, and PR preparation.

      Also in 3 projects that use this

    • GoogleSkill

      implement-issue

      Implement a Site Kit GitHub issue end-to-end from its implementation brief. Use when the user asks to implement, build, or work on a GitHub issue / feature by number (e.g. "implement issue #12345", "build the feature in issue 12345", "follow the implementation brief for #12345") in the google/site-kit-wp repo.

      Also in 9 projects that use this

    • +2 more from zerx-lab
    • +1 more from n24q02m
  • In this repository7 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.