PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.5)
Token size
378
Example input
[ISSUE_TYPE]: feature [ISSUE_TITLE]: Add dark mode toggle to dashboard [ISSUE_BODY]: Users want a dark mode option. Currently only light theme exists. The toggle should live in the settings panel. [CONTEXT_AND_CONVENTIONS]: $150 bounty, help wanted. Frontend uses Tailwind. Tests use Playwright. Settings live in /src/features/settings. [KNOWN_CONSTRAINTS]: Must not break existing theming system. Persist preference across sessions. Default to system preference if possible.
Example output
Example 1 - Feature request Before I start on this, I want to make sure I understand the expected scope. 1. Should this apply globally across the app, or only to the dashboard area mentioned in the issue? 2. Is there an existing settings or preferences pattern you want this to follow? 3. Should the user's choice persist across sessions, or is a session-only setting enough for the first version? 4. Are there any accessibility or contrast requirements I should treat as acceptance criteria? 5. Would you prefer a small first PR with the core behavior, then a follow-up for polish? Definition of done: - The setting is available in the expected location. - The selected behavior persists according to the agreed scope. - Existing tests are updated, or a small regression test is added. - Any user-facing change is reflected in docs or release notes if needed. Clarifying this up front should help avoid a PR that works technically but does not match the intended product behavior.
🤖 GPT

Maintainer Scope Questions

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.5
Tested icon
Guide icon
4 examples icon
Free credits icon
Ambiguous GitHub issues waste contributor time. This prompt helps maintainers, bounty owners, and open-source contributors clarify scope before anyone starts coding. Paste an issue title, body, labels, bounty context, and known repo constraints. The prompt returns a respectful GitHub comment that asks the right scope questions and proposes a tentative definition of done. It helps clarify: - What is in scope and out of scope - Which APIs, files, modules, or behaviors may change - Compatibility
...more
Added 1 week ago
Report
Browse Marketplace