Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Model notes: Works with, and your own note on a version

Open
  • Is something wrong?
#58 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, markdown, sqlite
Domain
api, cli, database, desktop

Research direction

Start by reading ROADMAP.md and the existing VersionNotes implementation, prompt metadata persistence and migration setup, plus the 1.0 fixtures. The issue requires decisions about model names, version notes, and CLI/MCP fields before implementation; record the settled answers as a dated decision in ROADMAP.md. Done when that decision is recorded and the issue has a milestone with its own checklist.

Written by the indexing model from the issue text.

Description

enhancement later

Prompts stop working after a model update, and today nothing records which model a prompt was tuned for. This brings back the design's "Works with" chips and adds a note you write yourself on a version.

What has to be settled before this gets a milestone

  • Works with. A list of model names on a prompt. It's metadata like tags, so changing it saves at once and makes no version. It needs a new column or table (a new migration, never an edited one) and an optional Markdown key that 1.0 files simply don't have.
  • Version notes. Each version already has a generated note, such as "Edited body (+3 −1 lines)" (VersionNotes). A written note sits beside it instead of replacing it, so the History tab and the 1.0 fixtures keep the generated text.
  • Free text or a list. Model names change fast, so a fixed list would go stale. Free text with suggestions from names already used is the likely answer.
  • CLI and MCP. Whether --json and the MCP answers gain the new fields. Added fields are fine under the promise; renamed ones aren't.

Done when

  • The settled answers are a dated decision in ROADMAP.md, and this issue gets a milestone with its own checklist.
Dominant language
C#
Stars
0
Forks
1
Avg merge
1h 21m
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hazeliscoding/prompuff

All issues in hazeliscoding/prompuff

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.