docs: add project badges to README

[clroot]

Summary

• Add CI status, crates.io, PyPI, Maven Central, license (MIT), and MSRV badges to both README.md and README.ko.md

Test plan

• Verify badge images render correctly on GitHub
• Confirm all badge links point to the correct destinations

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello @clroot, 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 significantly enhances the project's documentation by integrating various informational badges into both the English and Korean README files. These additions provide a quick, visual overview of the project's continuous integration status, package availability across different ecosystems, licensing, and Rust compatibility, thereby improving discoverability and clarity for users and potential contributors.

Highlights

• Project Badges Added: Introduced a comprehensive set of project badges to both the English and Korean README files.
• CI Status Visibility: Added a CI status badge linking to the GitHub Actions workflow, providing immediate insight into the project's build health.
• Package Manager Integration: Included badges for Crates.io, PyPI, and Maven Central, displaying current package versions and linking to their respective pages.
• License and MSRV Information: Added badges to clearly indicate the project's MIT license and its Minimum Supported Rust Version (MSRV).

Changelog

• README.ko.md
  • Added CI status badge
  • Added Crates.io badge
  • Added PyPI badge
  • Added Maven Central badge
  • Added MIT License badge
  • Added MSRV badge
• README.md
  • Added CI status badge
  • Added Crates.io badge
  • Added PyPI badge
  • Added Maven Central badge
  • Added MIT License badge
  • Added MSRV badge

Activity

• The initial changes were generated using Claude Code.
• A test plan was outlined to verify badge rendering and link correctness on GitHub.

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

The pull request adds a comprehensive set of project badges to both the English and Korean README files, covering CI status, package registries (Crates.io, PyPI, Maven Central), licensing, and MSRV. The badge links and image sources are correctly configured and consistent with the project's metadata. My feedback focuses on improving the visual layout of the README header by grouping the badges on a single line to reduce vertical space and improve readability.

[gemini-code-assist]

Grouping badges on a single line is a common practice to keep the README header concise. This ensures that the project description and other key information are visible without excessive scrolling.

Suggested change

	[](https://github.com/clroot/slimg/actions/workflows/release.yml)
	[](https://crates.io/crates/slimg)
	[](https://pypi.org/project/slimg/)
	[](https://central.sonatype.com/artifact/io.clroot.slimg/slimg-kotlin)
	[](https://opensource.org/licenses/MIT)
	[](https://www.rust-lang.org)
	[](https://github.com/clroot/slimg/actions/workflows/release.yml) [](https://crates.io/crates/slimg) [](https://pypi.org/project/slimg/) [](https://central.sonatype.com/artifact/io.clroot.slimg/slimg-kotlin) [](https://opensource.org/licenses/MIT) [](https://www.rust-lang.org)

[gemini-code-assist]

Grouping badges on a single line is a common practice to keep the README header concise. This ensures that the project description and other key information are visible without excessive scrolling.

Suggested change

	[](https://github.com/clroot/slimg/actions/workflows/release.yml)
	[](https://crates.io/crates/slimg)
	[](https://pypi.org/project/slimg/)
	[](https://central.sonatype.com/artifact/io.clroot.slimg/slimg-kotlin)
	[](https://opensource.org/licenses/MIT)
	[](https://www.rust-lang.org)
	[](https://github.com/clroot/slimg/actions/workflows/release.yml) [](https://crates.io/crates/slimg) [](https://pypi.org/project/slimg/) [](https://central.sonatype.com/artifact/io.clroot.slimg/slimg-kotlin) [](https://opensource.org/licenses/MIT) [](https://www.rust-lang.org)