agentleFS
Sign inStart free
LikeMindsCommunityLikeMindsCommunity/agentic-workflow-backend/.claude/skills/find-bugs/SKILL.md

find-bugs

Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub

Compare a GENERATED artifact against the EXPECTED one for a platform whose Knowledge Base (KB) documents what "correct" means, and record every genuine discrepancy as a row in that client's comparison sheet under `outputs/<client>/comparisons/`. The KB is the sole authority: entity types, properties, defaults, relationships, variables, patterns, numbered constraints, and every STRICT/MUST/NEVER directive are read from it at run time, so a KB that gained a rule yesterday is checked against today. Works on structured artifacts (JSON/YAML/XML/NodeFlow), documents (PDF/DOCX/MD/HTML), and tabular files, detecting the mode from the KB. Matches entities by their discriminator field, never by UUIDs or display names, and never flags free-form fields. Optionally checks the generated artifact against the source requirements document that produced it. Use when an operator has a generated artifact and a known-good counterpart and wants the differences that actually matter. Inputs: kb=<dir>, generated=<path>, expected=<path> (all required), source=<path>, comparison=<name>, output=<dir>. Triggers: "find the bugs in this generated file", "compare generated vs expected for {client}", "find-bugs", "check this output against the KB".

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gcp-cloud-run, conversation-memory and 9 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.
  • xfstudioSkill

    gcp-cloud-run

    Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub.

    Also in 3 projects that use this

  • xfstudioSkill

    conversation-memory

    Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.

    Also in 3 projects that use this

  • SentrySkill

    iterate-pr

    Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

    Also in 3 projects that use this

  • xenitV1Skill

    powershell-windows

    PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.

    Also in 3 projects that use this

  • abdullah1854Skill

    context-optimization

    Also in 3 projects that use this

  • SentrySkill

    code-simplifier

    Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.

    Also in 3 projects that use this

  • +1 more from getsentry

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 10 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 3

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

Check your setup, free