coyl
/ gemini-cli-git-analysis
Created
July 24, 2025 14:30
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Generate a detailed developer performance report by analyzing the Git logs for the last two months. | |
| **Primary Instructions:** | |
| 1. **Consolidate Aliases:** Before analysis, you must identify and consolidate statistics for any developers who have committed using different aliases (e.g., merge data for "Jane Doe" and "jdoe"). | |
| 2. **Execute Commands:** Run the five commands listed below to gather the necessary data. | |
| 3. **Apply Strict Evaluation:** Provide a detailed performance review for each developer on a 1-10 scale. The tone of the analysis and recommendations must be strict and critical, focusing on actionable feedback and adherence to engineering best practices. | |
| 4. **Use Specific Formatting:** The final report must strictly follow the detailed format, including all specified headers, tables, emojis, and star ratings. | |
| 5. **Save Output:** After generating the complete report, dump the entire output into a file named `report.md`. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /** | |
| * Invoke protected or private method of object | |
| * | |
| * @param object $object | |
| * @param string $method name of method to invoke | |
| * @param mixed $arg1 args that passed to invoked method [optional] | |
| * | |
| * @return mixed | |
| * |