Can this skill be used for security vulnerabilities?

No, security issues should be reported privately. If a security concern is detected, the skill will direct you to contact the security team via email instead.

How does it check for duplicate issues?

The skill uses the gh CLI to search both open and closed issues and discussions, presenting potential matches to the user before proceeding.

Why is the writing style described as 'fluff-free'?

To respect maintainers' time, the skill removes unnecessary apologies or preambles, focusing strictly on factual, actionable technical information.

Does this skill automatically create issues on GitHub?

No, it prepares a high-quality draft for manual submission, ensuring the user maintains final control over what is posted to the repository.

What information is required for a bug report?

It will prompt you for the Positron version, operating system, reproduction steps, expected vs. actual behavior, and any relevant error messages.

Positron Issue Creator

Name: Positron Issue Creator
Author: Activer007

byActiver007

Collaboration Tools

Drafts high-quality, actionable GitHub issues for the Positron IDE by automating duplicate searches and context gathering.

About

The Positron Issue Creator is a specialized workflow tool designed to streamline the contribution process for the Positron IDE. It guides users through a rigorous preparation process, including automated duplicate checking and label selection via the GitHub CLI, ensuring that every submission is high-value and triage-ready. By enforcing a terse, 'fluff-free' writing style and prompting for specific technical details like environment specs and reproduction steps, this skill helps developers and testers provide the exact information needed by the Positron team while maintaining manual control over the final submission.

Key Features

Iterative context gathering for bug reports and feature requests
Markdown file generation or clipboard-ready formatting for manual submission
0 GitHub stars
Dynamic label fetching for accurate repository triage
Strict 'fluff-free' writing guidelines for professional reports
Automated duplicate detection across GitHub issues and discussions

Use Cases

Checking for existing discussions before reporting a new problem
Reporting reproducible bugs with precise system info and error logs
Drafting feature requests with clear use cases and proposed behaviors

About

Key Features

Iterative context gathering for bug reports and feature requests
Markdown file generation or clipboard-ready formatting for manual submission
0 GitHub stars
Dynamic label fetching for accurate repository triage
Strict 'fluff-free' writing guidelines for professional reports
Automated duplicate detection across GitHub issues and discussions

Use Cases

Checking for existing discussions before reporting a new problem
Reporting reproducible bugs with precise system info and error logs
Drafting feature requests with clear use cases and proposed behaviors