Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Pyscn – Python code quality analyzer for vibe coders

github.com

Post reply on HN
Print view View original

81–87 of 87 posts

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#81

Post by d-yoda »

ktrnka wrote: post #75

Looks good to me! The status bar did something weird on my codebase in which 2% was really 100% so it looked like it was gonna take hours but only took a minute or so. I'll try hooking it into my refactor/cleanup workflow with copilot and see how it works as grounding.

Thanks for trying it out! For the progress bar bug, would you mind opening a GitHub issue with details? That'll help us track it down.

Great idea using it as grounding for AI-assisted refactoring! Let us know how that workflow goes.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#83

Post by d-yoda »

incomingpain wrote: post #79

I saw this project show up in some newsletters. Awesome project idea. I've been using 'vulture' so far. But when i try to run analyze or check. Running quality check... Complexity analysis failed: [INVALID_INPUT] no Python files found in the specified paths Dead code analysis failed: [INVALID_INPUT] no Python files found in the specified paths Clone detection failed: no Python files found in the specified paths Error…

Wow, was it really in some newsletters? That's awesome to hear, and would definitely explain the recent spike on GitHub!

Thanks a lot for the bug report and for providing the details. I have a hunch—it's possible that you need to explicitly specify the path depending on your directory structure. For example, if your Python files are under a src directory, could you try running it like [your_tool_name] analyze src/?

If that still doesn't solve the problem, it would be a huge help if you could open a quick issue on GitHub for this.

Thanks again for your feedback!

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#84

Post by d-yoda »

stuaxo wrote: post #76

Here are some anti patterns a colleague put in their code. Prescriptive comment: Comment describes exactly what the following code does without adding useful context. (Usually this is for the LLM to direct itself and should be removed). Inconsistent style: You have this across modules, but this would be in the same file. Inconsistent calling style: A function or method should return one kind of thing. (In the worst c…

This is super insightful, thank you for sharing. It's a great list of common LLM-generated anti-patterns.

I'd love to look into incorporating checks for these into pyscn. This is exactly the kind of stuff I want it to catch.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#85

Post by d-yoda »

Def_Os wrote: post #82

Nice idea, good timing. Any plans to wrap this in an MCP? My Claude Code instance should have this in their toolbox.

Yes, that's definitely something I'm looking into. I've received a few comments about AI coding integrations, so it's becoming a high priority.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#86

Post by incomingpain »

d-yoda wrote: post #83
incomingpain wrote: post #79

I saw this project show up in some newsletters. Awesome project idea. I've been using 'vulture' so far. But when i try to run analyze or check. Running quality check... Complexity analysis failed: [INVALID_INPUT] no Python files found in the specified paths Dead code analysis failed: [INVALID_INPUT] no Python files found in the specified paths Clone detection failed: no Python files found in the specified paths Error…

Wow, was it really in some newsletters? That's awesome to hear, and would definitely explain the recent spike on GitHub! Thanks a lot for the bug report and for providing the details. I have a hunch—it's possible that you need to explicitly specify the path depending on your directory structure. For example, if your Python files are under a src directory, could you try running it like [your_tool_name] analyze src/? I…

https://imgur.com/a/382mtPr

It was linked in the TLDR newsletter on monday.

(myglobalenv) steve@bird:~/PycharmProjects/netflow$ ls aggregator.py data netflow settings.py assets database.py notifications.py sniper.py config.py Dockerfile opencode.json start.sh context_manager.py integration.py __pycache__ tcpports.py context.py largflow.py README.md dashboard.py main.py requirements.txt (myglobalenv) steve@bird:~/PycharmProjects/netflow$ pyscn check . Running quality check... Complexity analysis failed: [INVALID_INPUT] no Python files found in the specified paths Dead code analysis failed: [INVALID_INPUT] no Python files found in the specified paths Clone detection failed: no Python files found in the specified paths Error: analysis failed with errors Usage: pyscn check [files...] [flags]

Flags: --allow-dead-code Allow dead code (don't fail) -c, --config string Configuration file path -h, --help help for check --max-complexity int Maximum allowed complexity (default 10) -q, --quiet Suppress output unless issues found --skip-clones Skip clone detection

Global Flags: -v, --verbose Enable verbose output

-v doesnt give me anything neither.

Re: Show HN: Pyscn – Python code quality analyzer for vibe coders

#87

Post by d-yoda »

incomingpain wrote: post #86
d-yoda wrote: post #83

Earlier quoted context omitted.

Wow, was it really in some newsletters? That's awesome to hear, and would definitely explain the recent spike on GitHub! Thanks a lot for the bug report and for providing the details. I have a hunch—it's possible that you need to explicitly specify the path depending on your directory structure. For example, if your Python files are under a src directory, could you try running it like [your_tool_name] analyze src/? I…

https://imgur.com/a/382mtPr It was linked in the TLDR newsletter on monday. (myglobalenv) steve@bird:~/PycharmProjects/netflow$ ls aggregator.py data netflow settings.py assets database.py notifications.py sniper.py config.py Dockerfile opencode.json start.sh context_manager.py integration.py __pycache__ tcpports.py context.py largflow.py README.md dashboard.py main.py requirements.txt (myglobalenv) steve@bird:~/Pych…

Thanks! I will fix the issue as soon as I can in the next version.
Post reply on HN