AI Prompts

Report.MD

Report generation

Prompt : In the spirit of corporate "need" for reports and "status" updates (ya know, instead of talking to people and knowing what's going on) -- we have to create our monthly report. Using this file for the instructions, generate this report.

This is what you have trained for. Make us proud.

---

Instructions:

Run the following git command on each repo under this directory, using this as an example.

git -C /c/project log --oneline --since="2025-08-01" --until="2025-08-31"

Use the previous month.

If no changes happened during that period of time, ignore it and exclude it from the report.

Generate a Business Beige Report

If git is present, treat each directory as its own project.

Limit this report to 5 items total. Judge the best ones and prioritize those.

Include the project name in the heading.

If multiple items were from the same project, consolidate them into the same heading.

Ignore <folders you don't want>

Make us look good. #1 rule, make us look good. Because we are. We are awesome.

Save this file to Report.MD to the same directory you found this file.

Open the file in vscode upon completion for review.

WhatsNew.md

How to get the latest Gemini CLI release notes

This document contains a prompt to get the latest release notes for the Gemini CLI.

Prompt

The Gemini CLI has been updated. I need to know what's new in the latest version.

Do not use pre-releases.
NO PRE RELEASES, only official releases.
Ask me what version I was on first.

1.  Fetch all version information from the npm registry for the `@google/gemini-cli` package.
2.  Filter out any releases that are marked as "prerelease" (e.g., "nightly", "preview", "rc") to identify the official releases.
3.  From the official releases, identify the most recent one.
4.  Fetch the release notes for the latest version from the GitHub releases API (`https://api.github.com/repos/google-gemini/gemini-cli/releases`).
5.  Analyze the release notes for the versions between the user's version and the latest version.
6.  Provide a summary of the key new features and improvements.
7.  Then, provide a direct, no-fluff summary of the most noteworthy changes for a technical audience. Focus on the "so what" for a developer. This should include:
    - Specific command changes (new flags, removed flags, behavior changes).
    - API changes for tool integration (new functions, deprecated functions, data structure changes).
    - Mention of specific performance improvements (e.g., "faster file hashing," "reduced memory usage during X operation").
    - Any changes to configuration files or environment variables.