Write a development recap without overstating progress

Supply an authorized activity export and time range to draft a recap that distinguishes proposals, reviews, merges and releases with evidence.

Execution environment and usage

AI / software

Gemini

Where to operate

The Gemini web-chat input; this version requests a text draft.

Getting started

  1. Open an eligible account at gemini.google.com and start a chat without connecting external accounts.
  2. Use public or authorized activity exports, a time range and author-confirmed context.
  3. Request the draft/check and compare it with the original material. Suggestions are not evidence of execution.

Setup and plan requirements

Task inputs: Use public or authorized activity exports, a time range and author-confirmed context. Use an eligible tool that can read the supplied format; verify parsing, context limits and access before relying on it.

Prompt portability limits

The written request can be adapted to a chatbot that accepts the same input. It does not transfer the original agent, plugins or computer permissions.

Usage limitations

This supplied-material exercise does not reproduce the original automation. Verify output, calculations and sources; regional/account availability is not guaranteed.

Environment sources

適用情境 / When to use

Supply an authorized activity export and time range to draft a recap that distinguishes proposals, reviews, merges and releases with evidence. Do not expose private repositories, customers or unreleased features. Commit counts are not personal-performance measures. Original case: The author-built challenge project uses Gemini for narration and deterministic code for some processing.

步驟 / Steps

  1. Use public or authorized activity exports, a time range and author-confirmed context.
  2. Separate proposed, reviewed, merged, released and unresolved work.
  3. Trace each outcome statement to records without inventing motives or reflections.

提示詞 / Prompt

From [authorized activity export/time range and timezone/confirmed context/audience/tone], draft a development retrospective. Distinguish proposed, reviewed, merged and released work and trace outcomes to records. Leave missing motives or impact for the author to supply. Do not reveal private information, infer performance or publish.

留意事項 / Cautions

  • Do not expose private repositories, customers or unreleased features.
  • Commit counts are not personal-performance measures.

來源限制 / Evidence limits

Scheduling was not reproduced; generated text does not establish public release or business impact.

流程說明 / Workflow note

These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.

原始工具組合 / Original tool stack

Gemini; Mastra; GitHub; Notion; DEV.to

Source checked: 2026-10-20

Turning Weekly GitHub Activity Into Blog Posts on Notion + DEV.to