I built a small Foundry helper: forge-scriptgen

[KimH4nKyul]

Hi Foundry team,

I built a small Rust CLI called forge-scriptgen and wanted to share it
here in case it looks useful.

Repo:
https://github.com/KimH4nKyul/forge-scriptgen

It generates script/*.s.sol deployment scripts from Solidity contracts in
a Foundry project.

The main reason I made it was that I kept repeating the same deployment
script setup work:

• find the target contract
• inspect the constructor
• write the script boilerplate
• wire constructor arguments manually

So I made a CLI that does that first pass for me.

A few things it supports today:

• contract discovery from src/**/*.sol
• constructor signature extraction
• script generation for normal deployment flows
• complex constructor inputs through raw Solidity literals
• reproducible fixtures for more complex Solidity cases

It has been tested against cases like:

• abstract contracts
• inheritance-based constructor modifiers
• multiline constructors
• struct arguments
• function-typed constructor arguments
• error declarations
• inline assembly
• misleading contract / constructor text inside comments and strings

Quick example:

forge-scriptgen --parser string-walker --list

forge-scriptgen \
  --parser string-walker \
  --args '[{"raw":"Config({owner: msg.sender, limits: [1, 2, 3]})"},
{"raw":"callback"},"primary",{"raw":"hex\"1234\""}]' \
  --private-key 0xabc123 \
  ComplexDeployment

I’m not trying to pitch this as a Foundry core change.

I just wanted to say: I made this, and if any of you have time to try it
once, I’d really appreciate it. Even a quick reaction on whether this feels
useful or unnecessary would help a lot.

If you think the idea has merit, I’d also appreciate feedback on:

• what feels clunky in the current UX
• what Solidity patterns would break your real projects
• whether this should stay external or aim for tighter ecosystem fit

Thanks. Any feedback would be genuinely helpful.