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

Prompt relationships and includes

Open
  • Is something wrong?
#57 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
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, sqlite
Domain
database, desktop

Research direction

Read ROADMAP.md, migration 5, and the near-variable tests referenced as issue #13 to understand the existing prompt relationships and compatibility constraints. The issue is done when the open design questions are answered in a dated ROADMAP.md decision and the issue has a milestone with its own checklist.

Written by the indexing model from the issue text.

Description

enhancement later

Link prompts beyond "Duplicated from", and let one prompt include another, so a shared preamble or a house style lives in one place.

Lineage today is Prompts.ParentPromptId (migration 5), set by Duplicate. It doesn't travel in Markdown, because imports are always independent copies.

What has to be settled before this gets a milestone

  • The 1.0 promise. get and render must print the same text for every 1.0 library. A body that holds any include syntax today renders literally, so includes can't start expanding inside existing prompts. Either a prompt opts in through an optional metadata key, or expanding is a new option that defaults to off.
  • Syntax or metadata. ROADMAP.md keeps new variable options out of {{…}}. Includes would need the same care, and the near-variable tests (#13) show what must stay plain text.
  • What travels. Whether an include survives export and import, by ID or by title, and what happens when the included prompt isn't in the library being imported into.
  • Loops and deletes. A prompt that includes itself through others, and an included prompt that's sent to Recently deleted or removed for good.
  • Kinds of relationship. Whether "see also" or "variant of" links are worth it beside includes.

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.