agentleFS
PostHogKnown publisherPostHog/posthog/.agents/skills/verifying-changes/SKILL.md

verifying-changes

Skill41k starsChanged 2 days agoLicence not identifiedView on GitHub

Picks the cheapest check that is enough to confirm a change works, and says when a slower one is needed. Use before you report a task done, before you start Storybook, the dev stack or a Playwright run to check your own work, and when you are unsure how much verification a diff needs. Maps each kind of change, such as pure logic, DRF serializer or viewset, migration, kea logic, React component, CSS, Django template, CI workflow, SQL or HogQL, or docs and skills, to the layer that is enough and the layer that is wasted. `hogli verify --changed` runs the cheap layers for the current diff and names the slower ones left to run yourself. Trigger terms: verify, how do I test this, is this enough testing, start the stack, render it, run e2e.

6 other projects use a version of this.

Trending

Less talk lately.about the whole repository

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

Most recently taken up by

Who's talking about PostHog/posthog

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

See all 45

Talked about on YouTube, Bluesky, GitHub, Hacker News and Stack Overflow (45 times).

On YouTube · 17

12 more on YouTube

On Bluesky · 11

6 more on Bluesky

On GitHub · 9

4 more on GitHub

On Hacker News · 4

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    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 5 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.

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.