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 adds a new JSON file hgrp.pm/ProjectStatus.json to track the status of the 'chaos-coder' project, including tasks and overall progress. It also introduces a Cline rule update-project-status-on-task-change.yaml that automatically updates the project status in the JSON file whenever a change is detected. The rule uses a Node.js script (scripts/updateProjectStatus.js) to calculate the overall percentage done and then commits and pushes the changes using a cline-bot user.

Highlights

• Project Status Tracking: Adds a JSON file to track project status, tasks, and overall progress for the 'chaos-coder' project.
• Automated Status Updates: Implements a Cline rule to automatically update the project status in the JSON file whenever changes are made, using a Node.js script to calculate progress.

Changelog

• .cline/rules/update-project-status-on-task-change.yaml
  • Created a Cline rule to trigger updates on changes to the ProjectStatus.json file.
  • Configured the rule to run a Node.js script to calculate the overall percentage done.
  • Set up the rule to commit and push changes to the repository using a dedicated cline-bot user.
• hgrp.pm/ProjectStatus.json
  • Added a new JSON file to track project status, including project name, last updated timestamp, tasks with their status and percentage done, and overall percentage done.

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 tale,
Of tasks and progress scale,
Cline's bot takes flight,
Updating day and night,
Automation will not fail.

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 to update project status based on changes to the ProjectStatus.json file. The rule triggers a script to calculate the overall project progress and commits the 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 in the workflow. If the script fails, the workflow will continue, potentially leading to incorrect project status updates.
• Hardcoded email and user: The git config commands use hardcoded email and user names. This might not be ideal for all scenarios and could be made configurable.

Merge Readiness

The pull request is not ready for merging due to the missing error handling and hardcoded values. These issues should be addressed before merging to ensure the reliability and flexibility of the automation rule. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging.