Skip to content

fix: prevent @fill from inferring wrong Linear ticket references #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
factory-nizar wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

fix: prevent @fill from inferring wrong Linear ticket references #73

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/create-prompt/templates/fill-prompt.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,7 @@ Procedure:
Use the gathered information to write the description:
- Base every statement on verified changes from the diff and context you collected.
- Preserve important details already present in the existing description (ticket numbers, custom sections, links, manual notes). If uncertain about a detail, keep it as-is.
- Do NOT infer, guess, or add ticket references (Linear, Jira, GitHub issues, etc.) that are not already explicitly present in the existing PR description, PR comments, or branch name. Never extract ticket IDs from commit messages or other indirect sources. If no ticket is linked, leave the section empty or omit it entirely.
- Remove any placeholder text such as "@droid fill" before submitting.
- Keep the tone concise and factual. Use clear Markdown headings/bullets.
- If a template is available, fill it out; otherwise structure the output as:
Expand All @@ -36,7 +37,6 @@ Use the gathered information to write the description:
## Implementation Details (optional when not applicable)
## Testing
## Breaking Changes (only when relevant)
## Related Issues
- For sections you cannot verify, write "[To be filled by author]".

Submission:
Expand Down
Loading