reflect

Name: reflect
Author: bs1gr

Create a concise retrospective on how a coding or debugging session went, focusing on process, evidence, and improvements.

by bs1gr(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Prompt file imported from bs1gr/AUT_MIEEK_SMS (.github/prompts/reflect.prompt.md). Copyright stays with the author.

Create a short, practical reflection about the current or described session.

Focus on how the work was done, not just what changed.

Cover:

what worked well
what slowed things down or caused confusion
whether verification was strong enough
what should be repeated next time
what should change next time

Repository-specific guidance:

Prefer evidence-backed reflection over vague impressions
Do not create a new file unless the user explicitly asks to save the reflection
Do not create extra status or planning documents by default
If verification was weak or incomplete, say so plainly

Output format:

Session reflection

What worked

Bullet list

What didn’t

Bullet list

Evidence quality

Short assessment of how strong the verification was

Next-time improvements

Bullet list

Keep it concise and practical.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

Create a short, practical reflection about the current or described session.

Focus on **how** the work was done, not just what changed.

Cover:
- what worked well
- what slowed things down or caused confusion
- whether verification was strong enough
- what should be repeated next time
- what should change next time

Repository-specific guidance:
- Prefer evidence-backed reflection over vague impressions
- Do not create a new file unless the user explicitly asks to save the reflection
- Do not create extra status or planning documents by default
- If verification was weak or incomplete, say so plainly

Output format:

## Session reflection

### What worked
- Bullet list

### What didn’t
- Bullet list

### Evidence quality
- Short assessment of how strong the verification was

### Next-time improvements
- Bullet list

Keep it concise and practical.

Manifest

The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.

bs1gr-aut-mieek-sms-reflect-prompt.prompt.jsonjson

{
  "prompt": "Create a short, practical reflection about the current or described session.\n\nFocus on **how** the work was done, not just what changed.\n\nCover:\n- what worked well\n- what slowed things down or caused confusion\n- whether verification was strong enough\n- what should be repeated next time\n- what should change next time\n\nRepository-specific guidance:\n- Prefer evidence-backed reflection over vague impressions\n- Do not create a new file unless the user explicitly asks to save the reflection\n- Do not create extra status or planning documents by default\n- If verification was weak or incomplete, say so plainly\n\nOutput format:\n\n## Session reflection\n\n### What worked\n- Bullet list\n\n### What didn’t\n- Bullet list\n\n### Evidence quality\n- Short assessment of how strong the verification was\n\n### Next-time improvements\n- Bullet list\n\nKeep it concise and practical.",
  "variables": [],
  "notes": "Create a concise retrospective on how a coding or debugging session went, focusing on process, evidence, and improvements.",
  "metadata": {
    "source": {
      "provider": "github-prompts",
      "repository": "https://github.com/bs1gr/AUT_MIEEK_SMS",
      "path": ".github/prompts/reflect.prompt.md",
      "ref": "ddf24ac3a3a488c544218316e1e45b9c44a11ffa",
      "url": "https://github.com/bs1gr/AUT_MIEEK_SMS/blob/ddf24ac3a3a488c544218316e1e45b9c44a11ffa/.github/prompts/reflect.prompt.md",
      "key": "bs1gr/AUT_MIEEK_SMS/.github/prompts/reflect.prompt.md"
    }
  },
  "model_hints": [
    "GPT-5.4"
  ]
}

Fetch it by URL: GET /api/v1/registry/bs1gr-aut-mieek-sms-reflect-prompt/manifest?version=1.0.0