chore: add fmt cmd for outputs

[toaction]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @toaction, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the llpyg tool by integrating an automated Go code formatting step into its generation process. After the LLGo bindings are generated and the Go module is tidied, the tool will now automatically apply standard Go formatting to the output, ensuring code consistency and readability without manual intervention.

Highlights

• Automated Code Formatting: A new utility function, codeFormat, has been introduced to automatically format Go code within a specified output directory using go fmt ./....
• Integration into Main Workflow: The newly added codeFormat function is now called in the main function of llpyg.go, ensuring that all generated Go bindings are automatically formatted after module tidying.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a code formatting step using go fmt for the generated Go bindings, which is a great enhancement for code quality. The implementation introduces a new codeFormat function. My review provides a suggestion to refactor this new function to avoid changing the process's global state and to align with idiomatic Go error handling practices.

[niupilot]

Code Review Summary

This PR successfully adds automatic Go code formatting to the llpyg tool - a valuable enhancement for code quality. The implementation follows existing patterns well and integrates cleanly into the workflow.

Key findings:

• ✅ Code quality and structure are solid
• ⚠️ One security concern regarding directory traversal (see inline comment)
• ⚠️ Missing error handling for formatting failures
• 📝 Minor documentation improvement needed

Performance impact: Minimal overhead (~100-500ms for typical projects). The formatting step scales linearly with generated code size but shouldn't significantly impact build times.

Overall this is a good addition that will ensure generated bindings follow Go formatting standards.

[codecov]

Codecov Report

❌ Patch coverage is 44.11765% with 19 lines in your changes missing coverage. Please review.
✅ Project coverage is 48.27%. Comparing base (f84dd79) to head (5a7bad4).

Files with missing lines	Patch %	Lines
cmd/llpyg/llpyg.go	0.00%	14 Missing ⚠️
cmd/llpyg/utils.go	75.00%	2 Missing and 3 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #40      +/-   ##
==========================================
+ Coverage   44.46%   48.27%   +3.80%     
==========================================
  Files           6        6              
  Lines         452      464      +12     
==========================================
+ Hits          201      224      +23     
+ Misses        232      217      -15     
- Partials       19       23       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.