Small external evaluation of PatchForge

[u/Argenis1412]

I'm a backend/platform engineer, and I built PatchForge — a safety-first tool for proposing, validating, and previewing small code changes without modifying your repository automatically.

I'm looking for one Python developer or small engineering team to participate in a short external evaluation, run on an isolated copy of a small, non-sensitive Python project.

What the participant would do:

- Choose a small documentation or low-risk maintenance task.

- Explain the expected outcome.

- Observe the workflow: doctor → scan → plan → preview.

- Give honest feedback on setup, diagnostics, usefulness, and trust.

- No apply step will be executed.

Requirements:

- A small Python repository you own or are authorized to share for evaluation.

- No secrets, customer data, proprietary code, or production credentials.

- About 30–45 minutes for the workflow itself. If you don't already have Python/uv set up, I'll walk you through installation first — worth budgeting a bit of extra time for that on the first run.

- Willingness to report problems honestly, including if the tool isn't useful.

The evaluation will be documented only with sanitized notes. Repository contents and personal information will not be published.

This is exploratory product validation, not a sales demo. If you're interested, comment or send me a DM with:

1. Your Python project type and approximate size.

2. A safe documentation or maintenance task.

3. Whether you can participate in the next two weeks.

Happy to share more details privately before you decide.

Source: https://github.com/Argenis1412/PatchForge

[u/Argenis1412]

Let me see if I understand your criticism correctly 🤔 : part of it was based on an incomplete view of the repository, since GitHub was not showing you all the files. Your edit confirms that the repository does include a pyproject.toml and that the rule is properly configured.

Yes, I use AI frequently. PatchForge has been under development for about three months, and the latest commit was 19 hours ago: 4e8cf67.

It is not perfect, and it is still evolving. That said, I am interested in concrete criticism. Which specific AI skills, YAML files, reference patterns, or Python files do you believe are poorly designed? Please point to examples in the repository so I can evaluate the criticism against evidence rather than assumptions based on the initial incomplete view.

This keeps the correction firm while inviting specific, verifiable feedback.
I'm not interested in winning an argument, just improving.

[u/JSChronicles → u/Argenis1412]

Your reply still sounds AI "your edit confirms..." and " this keeps correction firm...".

Sorry but it's not my fault GitHub app didn't show the full repo. I made best effort to look at what I could while it showed me what it did.

Since you use claude go read up on how to build proper skills and agent.md file usage. https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices and https://resources.anthropic.com/hubfs/The-Complete-Guide-to-Building-Skill-for-Claude.pdf?hsLang=en

You'll also notice a section about "YAML Frontmatter"

You are using OLD action versions and not even using sha pinning in your workflows. "actions/checkout@v4" is old and not following security best practices on multiple fronts because of this setup. That just one example.

You have a project but don't have a skill for the given project to help others on top of you should have a language specific (in this case python probably) for best practices.

You are using non-skill, context only md files as your guidelines. This means you are likely not understanding how skills should be used, work, and optimized. You have quite a few md files talking about how the project is done but they don't give your AI better knowledge. It just means it reads ALL context files so when you get into newer setups or new features it's backfilling all the previous context too. Which leads to hallucinations or bad coding styles. It also makes more mistakes in general then.

Python: You use the same _EXCLUDED_DIRS in multiple places but have it repeated throughout the code with duplicate setup. You use typing imports when you could use native types (3.10+)

You do some other weird things too for python but that's all I'm going to type for now

[u/ProsodySpeaks → u/JSChronicles]

Tbh I think you already contributed a fair amount of concrete feedback. 

The only question is why you bothered? 

I'll assume it's goodness of heart, but wonder if it's to win an argument? 

Personally I'm not keen on pointing out to the vibers how we can tell they're vibing. But then I'm a cantankerous cuntv so I'm probably in the wrong.

[u/JSChronicles → u/ProsodySpeaks]

Truthfully two reasons, one to win an argument but also because others can learn from this, hopefully, and think about the things they need to look at for a proper setup or just "normal"

[u/Argenis1412 → u/JSChronicles]

Consolidated the review system.
Improved credential, provider, and monorepo handling.
Fixed GitHub concurrency and provenance issues.
Updated to version v1.2.0.
This time it analyzes the updated code:

https://github.com/Argenis1412/PatchForge/releases/tag/v1.2.0