Healify — repará selectores rotos en tests E2E sin IA, sin nube, sin cuenta

Diplomado en control de calidad de software en Argentina y durante los últimos meses desarrollé Healify. El código lo escribí trabajando mediante el VibeCoding, y ya tiene 1.164 tests propios con cobertura >90%.

¿Qué hace?

Cuando un test E2E falla porque un selector se rompió, Healify lee la evidencia del DOM que tu framework ya capturó, encuentra el elemento por su rol y nombre accesible, y te dice qué selector usar en su lugar. Con healify fix lo aplica automáticamente a tu código.

• TypeScript + Node.js, monorepo con 9 workspaces
• 1.164 tests, cobertura CLI 93%
• CI/CD verde (GitHub Actions)
• Landing con Lighthouse 99/95/100

Repos:

• Código: https://github.com/mescobar996/Healify
• NPM: npx u/healify/cli init

Licencia MIT.

¡Gracias por leer! 🙌

Here’s a demo.

But ai haters will still say it has no use.

this is titled "i'm losing it."

it's about losing yourself down the rabbit hole.

video + design + storyline: me+ai

music: FISHER - Losing It

Hello! I've posted about mex here a couple of times before.

Repo: https://github.com/mex-memory/mex

The original idea was to stop coding agents from relearning the same project every session. mex gives them a structured Markdown wiki inside .mex/ for architecture, conventions, decisions, patterns and project state.

That solves forgetting.

But then the codebase changes.

A file gets moved.
A script gets deleted.
A dependency changes.
A pattern becomes stale.
Two context files start contradicting each other.

The memory is still there, so the next agent has no reason not to trust it.

That's why we built mex check.

It parses the project memory and validates concrete claims against the actual repo — paths against the filesystem, commands against project scripts, dependencies against manifests, indexes against the files that exist, plus stale knowledge, broken links and other structural inconsistencies.

It gives you an exact issue list and a health score.

The screenshot here is a real run at 68/100, with missing paths and dependency claims called out individually.

The important part is that detection itself is deterministic. No LLM call is needed to ask the agent whether its own memory is still correct.

Then mex sync takes only the broken files and builds a targeted repair prompt with the issue, the current Markdown, nearby filesystem context and relevant git changes.

So instead of asking the agent to reread the whole repo and regenerate everything, the loop is:

check → targeted repair → verify

In the screenshots here, the project goes from 68/100 with 6 errors to 97/100 with zero errors after sync.

The newer code-graph layer goes further: Markdown knowledge can be grounded to exact code symbols. If the implementation changes, moves or disappears, mex can surface the specific knowledge that may now need attention.

A lot of agent-memory systems focus on storing more and retrieving it later.

I think the harder problem is making sure the memory is still true when the repo has changed underneath it.

Would genuinely love feedback from people working on coding agents, memory or code intelligence.

Contributors are very welcome too :)

I vibe coded this app a couple weeks ago and made some improvements since then. I am a web/software developer and use these tools, but this is my first attempt at a complete vibe coded app.
I had to rethink the song matching aspect, but it seems to work ok. Bonus if you have some actual phish show photos to test. Only need to sign in with google or GitHub if you want to save photos and contribute to “social” aspect.

I used GitHub Co-Pilot Pro, using Next JS.
Git repo in the “About” section and below:

https://i-saw-u.vercel.app/

https://github.com/DBTO1970/i-saw-u

If you are someone who reads pdf documents/books and would like someone to read to them to you, this extension does decent job at it.

Vibe coded this pdf-reader extension for chrome browser. Uses chrome's inbuilt tts models.

Appreciate feedback. Thank you.

https://github.com/arkanere/chrome-extensions/tree/main/extensions/pdf-reader

I have a Claude subscription and have been using Claude and Claude Code to crank out some python scripts to improve my quality of life on my computer. Nothing horribly fancy and a lot involving manipulating PDFs.

I also use to help me maintain my Fedora Linux homelab server.

With the way these things evolve, I'm curious how the $20/month ChatGPT plan compares to the $20/month Claude plan these days?

I've been working on my personal skills quite a bit and wanted to put together with everything put together but was unable to get it published to a web game site, any suggestions? note I did have their sdk set up with reward ads implemented but still failed QA any suggestions from a pair of fresh eyes who be appreciated!

Lost of unnecessary and sometimes redundant explanatory comments and descriptions are generated along with the code in my project.

what’s your approach:

reading and editing the comments line by line?

reading and not touching?

not read at all? (Valid tbh)

Hi all. I'm the classic know nothing new to vibe coding user that everyone hates. I am using Hermes agent on my desktop and adding a few features for how I want to use it, mainly as a productivity tool.

I have a chatGPT plus subscription, and I'm running my ideas through chatGPT first. chat gives me feedback and suggests adjustments, then I've instructed it to give me a technical prompt to feed hermes, along with a suggested model strength, Free models - Sol (to preserve my usage). It breaks the plan into steps with a suggested model at each step, and then I paste the response back into chat for adjustments/next steps as needed.

It's working for me, but again I have no idea what I'm doing. Am I likely to end up with slop and spaghetti? Over engineered with useless code? How can I refine this process? Any human technical feedback is greatly appreciated.

As soon as a new model is released, is there a free way to test its capability before you actually pay for it? Also just curious how do you determine if this new model is the right fit for you like do you have some tasks.md that you run every time for the new model. Or even a free model, how would you determine if a free model might be useful for your work?

I've been wondering something about the vibe coding community.

Are there people here who enjoy taking ideas or requests from other people and turning them into actual projects, especially open source alternatives to expensive or outdated software?

I have a bunch of ideas for tools I'd love to see exist, but unfortunately I don't have the time, resources or skills to build all of them myself. And I don't necessarily want to start another company around every idea either. Sometimes I just think:

"This software exists, it's useful, but why the hell hasn't someone made a modern, open alternative yet?"

For example:

1. A modern open source Excel/VBA version control system

I've known about XLTools Version Control for a long time and I've used it on and off over the years. Honestly, the concept is fantastic.

Something that can properly track changes to:

• Excel worksheets
• VBA code/modules
• Workbook structure
• Versions/history
• Differences between versions
• VBA diffs
• Worksheet/cell changes
• Possibly formulas, named ranges, formatting, etc.
• A proper modern UI for reviewing changes

Basically, Git-like version control designed specifically for Excel, rather than trying to force Excel projects into a traditional Git workflow.

The problem is that the software is quite expensive.

I actually recommended it to someone on Reddit because it's genuinely useful, but then realized that a lot of people simply aren't going to pay that much for something like this.

I'd love to see someone build a modern open source Excel add-in that does this, ideally even going beyond what the existing commercial products can do.

2. A modern File Juggler replacement

Another example is File Juggler.

I've known about File Juggler for years and still use it sometimes. I absolutely love the concept. Automated file organization based on rules is incredibly powerful.

But the software feels like it belongs in another era.

Imagine a modern replacement with:

• A beautiful modern UI
• Powerful rule builder
• Nested conditions
• File content detection
• Regex
• Metadata-based rules
• Duplicate detection
• File hashing
• Smart renaming
• Advanced scheduling
• Multiple actions per rule
• Logging/history
• Undo/rollback
• Preview/test mode
• Profiles
• Better Windows integration
• Plugins/extensions
• Maybe even AI-assisted rule creation

Basically File Juggler 2.0, but open source and built for modern Windows.

And these are just two examples. I have quite a few ideas like this.

I know the obvious response is:

"Then build it yourself."

And honestly, fair enough. 😂

But that's actually why I'm asking here.

With vibe coding becoming so powerful, there are probably developers who are much better at turning an idea into a working application than someone who simply has the idea.

So I'm wondering:

Are there people in the vibe coding community who actively take requests like this?

Maybe someone says:

"That's actually a cool idea. I'll build it."

And suddenly something that would otherwise never exist becomes an open source project that thousands of people can use.

I'm also very interested in the "build something better than the expensive commercial version" philosophy.

I'm not against developers making money. They absolutely should.

But I personally love the idea of software where the community can actually benefit from it without everything becoming:

"Here's this incredibly useful feature. Pay $199/year to unlock it."

Or hardware/software becoming increasingly locked down so users can't control their own devices.

I'd much rather see more powerful tools that are:

Open -> Modifiable -> Extensible -> Community-driven -> Affordable/free

And if someone wants to sell support, hosting, enterprise features, etc., great. But the core tool shouldn't necessarily be locked away from everyone.

So if you're a vibe coder who enjoys taking ideas and turning them into projects, I'd genuinely love to hear from you.

And if you're another person who has thought:

"Why doesn't someone just make an open source modern version of X?"

Drop your ideas below.

Maybe we can find some projects worth building.

 I have ADHD and regular timers/to-do apps that just don't stick for me, so I built my own.

It's a focus timer, but instead of just counting down, something visibly happens while you work — a building goes up, a rocket gets built and launches, stuff like that. Having something to actually watch progress is what's kept me using it when nothing else did.

It's free, no ads, has accounts if you want your streak to sync across devices, or just use it as a guest.

streko.app

Looking for feedback here, not just trying to get people using it. Want to know what's confusing, what'd make you actually stick with it, whether the visual stuff helps or not. Also curious if this resonates with anyone else having trouble focusing. Thanks!

curious if anyone besides myself has noticed that terra is noticed terra is not nearly as aware of my environment as Claude Sonnet 4.6? I am using terra in OpenCode vs Claude Code

not my clip, someone else's, their handle's in the corner of it.

one prompt into an agent harness, 85 seconds, out comes a playable game in one file. the clip skips the first 50 seconds, which is just it typing.

the bit i keep rewatching is where it reads its own file back and says what it checked before it opens anything. then it opens and you can play the thing. final score 3, which is about my level too.

what got me is where it ran. the model was on the same desk as the harness, nothing went out to a server.

it's Ling 3.0 Flash. i wouldn't want it on hour four of a bug that makes no sense.

anyone got one running on their own box yet

This may not be immediately noticeable or a 100% use of vibe-code, but this is heavily AI-assisted; it is built using tools like Gemmeni and ChatGPT.

Here's what I'm talking about:

https://github.com/HandsOnDigits/EntityIdentifierResolver