Skip to content

chore: sync files from commit#69

Closed
kubrickcode wants to merge 1 commit intomainfrom
sync/commit-1763233367690
Closed

chore: sync files from commit#69
kubrickcode wants to merge 1 commit intomainfrom
sync/commit-1763233367690

Conversation

@kubrickcode
Copy link
Owner

Automated file sync via baedal push

Sync: commit

@gemini-code-assist
Copy link

Summary of Changes

Hello @kubrickcode, I'm Gemini Code Assist1! 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 introduces comprehensive documentation for a new Conventional Commits Message Generator. The primary goal is to standardize commit messages across the project by providing clear, detailed instructions and an automated process for generating messages that adhere to the Conventional Commits specification. This initiative aims to enhance the readability of the commit history, facilitate automated changelog generation, and ensure consistency in how code changes are described, thereby streamlining development workflows and improving project maintainability.

Highlights

  • New Conventional Commits Generator Documentation: A new markdown file, claude/commands/commit.md, has been added. This document introduces a tool designed to generate Conventional Commits-compliant messages in both Korean and English.
  • Comprehensive Commit Message Guidelines: The new documentation provides extensive guidelines on Conventional Commits, covering available types (e.g., feat, fix, chore), a decision tree for type selection based on file patterns, and detailed examples for various commit message complexities.
  • Automated Issue Linking and Output: The generator is designed to automatically append 'fix #N' to commit messages if the branch name corresponds to an issue number. The generated messages, in both languages, are saved to a commit_message.md file for easy review and copying.
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.

@kubrickcode kubrickcode deleted the sync/commit-1763233367690 branch November 20, 2025 01:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant