Add Agent Git Workflow skill page

[obrera]

Summary

• add a new Agent Git Workflow skill page under skills/
• cover branch naming, one PR/one commit discipline, PR hygiene, review-loop operations, CI gates, merge strategy, and post-merge cleanup
• explicitly clarify that obrera is used as an example GitHub handle prefix in branch name examples
• add the new page to the skills index list

Validation

• bun run build

[gemini-code-assist]

Summary of Changes

Hello @obrera, 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 introduces a new documentation page outlining a standardized and efficient Git and Pull Request workflow designed for agents. The goal is to promote clean commit history, faster reviews, and safe merges by providing clear guidelines on various stages of the development process, from branch creation to post-merge cleanup. This enhancement aims to improve consistency and collaboration within the development team.

Highlights

• New Skill Page Added: A new skill page titled 'Agent Git Workflow' has been added, providing guidelines for a practical Git and Pull Request workflow.
• Comprehensive Workflow Coverage: The new page covers essential aspects of a Git workflow, including branch naming conventions, the 'one PR/one commit' discipline, PR hygiene, review-loop operations, CI gates, merge strategy, and post-merge cleanup.
• Example Handle Clarification: The document explicitly clarifies that 'obrera' is used as an example GitHub handle prefix in branch name examples, and should be replaced with the user's own handle.
• Skills Index Update: The main skills index page has been updated to include a link to the newly added 'Agent Git Workflow' documentation.

Changelog

• src/content/docs/skills/agent-git-workflow.md
  • Added a new documentation page detailing the 'Agent Git Workflow'.
• src/content/docs/skills/index.md
  • Updated the skills index to include a link to the new 'Agent Git Workflow' page.

Activity

• Content synchronization and static site generation were successfully completed.
• Vite built client assets in 235ms.
• Static routes were generated, including the new '/skills/agent-git-workflow/index.html'.
• A search index was built with Pagefind, finding 15 HTML files.
• A sitemap was created and markdown files were copied.

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 introduces a new documentation page for the 'Agent Git Workflow', outlining best practices for a clean and efficient development cycle on GitHub. The changes are well-structured and clear. I've added a couple of suggestions to the new markdown file to further improve clarity and consistency regarding git operations during the PR lifecycle.

[obrera]

@gemini-code-assist please review

[gemini-code-assist]

Code Review

The pull request introduces a new skill page for 'Agent Git Workflow' and updates the skills index. The new page provides clear guidelines for Git and PR workflows, covering branch naming, commit discipline, PR hygiene, review loops, CI gates, merge strategy, and post-merge cleanup. The content is well-structured and provides practical advice for OpenClaw agents. The changes are straightforward and improve the documentation. The AI's comments are relevant and helpful, and none contradict the provided rule.

[obrera]

@gemini-code-assist please review

[gemini-code-assist]

Code Review

The pull request introduces a new skill page for 'Agent Git Workflow' and integrates it into the skills index. The new page provides a comprehensive guide on Git and PR workflows, covering branch naming, commit discipline, PR hygiene, review loops, CI gates, merge strategy, and post-merge cleanup. The changes are well-structured and provide valuable documentation for agents. I've identified a few areas for improvement regarding clarity and consistency in the documentation, which are reflected in the comments.