Make repetitive scaffolding and code review feel like typing a slash
command.
I just pushed a tiny open‑source project that’s been sitting in my
toolbox for a while: Tal7aouy Developer Skills – a collection of
Claude/AI‑driven helpers (php-dev-helper, node-dev-helper,
laravel-dev-helper) you can run from the shell or directly in the
Claude/VS Code/​Cursor chat.
Each helper is basically a smart CLI that:
- scans your project’s source files
- suggests improvements, refactorings and boilerplate
- can generate controllers, routes, models, etc. based on your existing code
- writes “reports” to disk when you ask it to (
--file-output)
It’s not a security scanner or audit tool, it’s a developer
assistant – the kind that tells you, “hey, you’ve got inconsistent
naming here” or “that controller could be factored into a service.”
Why I built it
I kept finding myself doing the same setup work:
- spin up a small CLI that can bundle a directory of files
- feed it to a model with some reference docs
- parse the output and show a nice markdown report
This repo packages that pattern as three reusable helpers, each tuned to
a language/framework. Along the way I ripped out all of the original
Solidity/auditor baggage – it’s now purely for devs.
Quick start
git clone git@github.com:tal7aouy/skills.git
mkdir -p ~/.claude/commands && cp -r skills/*-helper ~/.claude/commands/
# (or put them in ~/.cursor/skills/ for Cursor)
# in a project:
php-dev-helper # scan everything
php-dev-helper deep # add extra adversarial reasoning
php-dev-helper generate controller Foo
php-dev-helper app/Models/User.php # review one file
In the Claude/VS Code/​Cursor chat window type the same commands with a
leading slash:
/php-dev-helper generate controller Foo
What it looks like
$ /php-dev-helper generate controller Foo
> Generated app/Http/Controllers/FooController.php
> Remember to add a route to routes/web.php
$ /php-dev-helper app/Models/User.php
> ⚠️ Inconsistent naming: UserModel vs User
> ✨ Suggestion: simplify to User and update related imports
The helpers are smart enough to ignore vendor/, node_modules/,
tests/, etc., and they produce a Markdown report that you can save
into assets/reports/ for later review.
Repo structure and customization
Each helper lives in its own directory under the repo root. You can
clone them individually into ~/.claude/commands/ or
~/.cursor/skills/. They are completely self‑contained, and you can
tweak the prompts, templates, or add your own pattern files in
references/patterns/.
Contributing
It’s still early work – I’ve stripped out all the “audit” language and
destined the project for developers, but it could use:
- better pattern examples (add your own to
references/patterns/) - improved agent prompts
- new generators (events, middleware, migrations, routes, etc.)
- support for other languages/frameworks
The repo already has issue & PR templates, a friendly license (MIT), and
CI that bumps helper versions automatically. Feel free to fork and make
it your own.
Final note
This isn’t magic – the AI is just a teammate that scans your code. Use
it for productivity, not as a replacement for review. If you build
something cool with it or have ideas for other helpers, I’d love to hear
about it.
Happy coding!
— Tal7aouy
Top comments (0)