Add hgrp.pm/ProjectStatus.json, Windsurf and Cline rules

[dholzric]

Automated PR to add status tracking and automation rules.

[gemini-code-assist]

Hello @dholzric, 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!

Summary of Changes

This pull request introduces a new Cline rule and a corresponding project status file to automate the updating of project status based on task changes. The rule monitors changes to the hgrp.pm/ProjectStatus.json file and triggers a script to recalculate the overall project completion percentage, committing and pushing the updated status.

Highlights

• New Cline Rule: A new Cline rule update-project-status-on-task-change.yaml is added to automate project status updates.
• Project Status File: The hgrp.pm/ProjectStatus.json file is created to track project name, last updated timestamp, tasks with their status and completion percentage, and the overall project completion percentage.
• Automation: The Cline rule triggers a script (scripts/updateProjectStatus.js) to calculate the overall project completion percentage whenever the ProjectStatus.json file is modified.

Changelog

• .cline/rules/update-project-status-on-task-change.yaml
  • Added a new Cline rule to monitor changes to hgrp.pm/ProjectStatus.json.
  • Configured the rule to run a script to update the project status.
  • Implemented automatic commit and push of the updated project status.
• hgrp.pm/ProjectStatus.json
  • Created a JSON file to store project status information.
  • Defined fields for project name, last updated timestamp, tasks, and overall completion percentage.
  • Initialized the file with sample data for an 'Image-Collage' project.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

---

A JSON file's born,
Cline rules watch, 'til the morn,
Status auto-set.

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 introduces a new automation rule and a project status file. The automation rule updates the project status whenever the ProjectStatus.json file changes. Overall, the changes seem reasonable, but there are a few areas that could be improved.

Summary of Findings

• Missing error handling: The script scripts/updateProjectStatus.js is executed without any error handling. If the script fails, the workflow will continue, potentially leading to incorrect project status updates.
• Hardcoded email and username: The git config commands use hardcoded email and username. While this might be acceptable for a bot, it's better to use environment variables or a configuration file to manage these settings.
• Missing newline at end of file: The file hgrp.pm/ProjectStatus.json is missing a newline at the end of the file. This is a common convention and should be added.

Merge Readiness

The pull request is not ready to be merged due to the missing error handling and hardcoded email/username. These issues should be addressed before merging. I am unable to approve this pull request, and other reviewers should review and approve this code before merging.