From 789dee58e5efaa1c8d3a315deadc88d4e973cf5c Mon Sep 17 00:00:00 2001 From: Really Him Date: Fri, 6 Nov 2026 21:17:03 -0500 Subject: [PATCH 1/6] fix(starter-buddy): scope security notices and add issue-form defaults Only the bug-report forms and the general report template carry the notice against publishing vulnerability details; the suggestion and documentation forms drop it. The chooser configuration template adds a security contact link to the policy, removed when no policy exists. Issue forms now prefill a title prefix ([BUG], [FEAT], [DOCS]) and one of GitHub's default labels (bug, enhancement, documentation), and the guidance asks for each label to be checked against the target repository. Co-Authored-By: Claude Opus 5.5 --- .../skills/community-health/SKILL.md | 2 +- .../.github/ISSUE_TEMPLATE/config.yml | 4 +++ .../variants/issues/documentation.yml | 5 ++-- .../variants/issues/guided-bug.yml | 2 ++ .../variants/issues/suggestion.yml | 5 ++-- .../variants/issues/technical-bug.yml | 2 ++ .../references/template-selection.md | 4 +-- .../references/templates-and-validation.md | 7 +++-- tests/starter-buddy/skill-evals.md | 30 +++++++++---------- 9 files changed, 34 insertions(+), 27 deletions(-) diff --git a/plugins/starter-buddy/skills/community-health/SKILL.md b/plugins/starter-buddy/skills/community-health/SKILL.md index 75d5694..faaedf6 100644 --- a/plugins/starter-buddy/skills/community-health/SKILL.md +++ b/plugins/starter-buddy/skills/community-health/SKILL.md @@ -42,7 +42,7 @@ Use `references/template-selection.md` for bundled options and `references/templ - **README:** Start with the project purpose and verified getting-started information. Expand or curate it according to the user's interest. - **CONTRIBUTING:** Describe accepted contributions and the project's actual setup, checks, and contribution process. -- **Issue templates:** Start with short forms for the selected categories and blank issues enabled. Adapt fields and routing to the project's needs. Direct vulnerability details to a private channel. +- **Issue templates:** Start with short forms for the selected categories and blank issues enabled. Adapt fields, labels, and routing to the project's needs. Direct vulnerability details to a private channel through the bug forms and the chooser's security contact link. - **PR template:** Start with the short variant and add detail where useful. - **License and conduct:** Fetch the selected canonical text and preserve its required notices. Resolve an existing licensing conflict before replacing text. - **SECURITY:** State the confirmed support scope and a working private route. If GitHub enablement is pending, keep that dependency clear before publication. diff --git a/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml b/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml index 0086358..c0de2f1 100644 --- a/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml +++ b/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml @@ -1 +1,5 @@ blank_issues_enabled: true +contact_links: + - name: Report a security vulnerability + url: "{{SECURITY_POLICY_URL}}" + about: Please report vulnerabilities privately, as described in the security policy, not in a public issue. diff --git a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/documentation.yml b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/documentation.yml index 768c5ce..9098520 100644 --- a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/documentation.yml +++ b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/documentation.yml @@ -1,9 +1,8 @@ name: Documentation correction description: Help us improve an explanation or resource +title: "[DOCS]: " +labels: ["documentation"] body: - - type: markdown - attributes: - value: "Do not publish vulnerability details in this issue. Use [the private reporting instructions]({{SECURITY_POLICY_URL}})." - type: input id: location attributes: diff --git a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/guided-bug.yml b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/guided-bug.yml index ac3f390..32c9238 100644 --- a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/guided-bug.yml +++ b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/guided-bug.yml @@ -1,5 +1,7 @@ name: Bug report description: Explain the behavior you encountered +title: "[BUG]: " +labels: ["bug"] body: - type: markdown attributes: diff --git a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/suggestion.yml b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/suggestion.yml index 57e30e7..7bd830a 100644 --- a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/suggestion.yml +++ b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/suggestion.yml @@ -1,9 +1,8 @@ name: Suggestion description: Propose a useful improvement +title: "[FEAT]: " +labels: ["enhancement"] body: - - type: markdown - attributes: - value: "Do not publish vulnerability details in this issue. Use [the private reporting instructions]({{SECURITY_POLICY_URL}})." - type: textarea id: need attributes: diff --git a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/technical-bug.yml b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/technical-bug.yml index 653c7e9..280ad49 100644 --- a/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/technical-bug.yml +++ b/plugins/starter-buddy/skills/community-health/assets/template-parts/variants/issues/technical-bug.yml @@ -1,5 +1,7 @@ name: Technical bug report description: Share a reproduction and the setup where it occurs +title: "[BUG]: " +labels: ["bug"] body: - type: markdown attributes: diff --git a/plugins/starter-buddy/skills/community-health/references/template-selection.md b/plugins/starter-buddy/skills/community-health/references/template-selection.md index 57187fb..0bdfe9f 100644 --- a/plugins/starter-buddy/skills/community-health/references/template-selection.md +++ b/plugins/starter-buddy/skills/community-health/references/template-selection.md @@ -39,8 +39,8 @@ Give a short file list with destinations and any commitments the files introduce Preserve recognized existing locations. Default new README, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT, and LICENSE files to the repository root. If the user prefers `.github/` or `docs/`, use those for supported community documents; keep the repository license at the root and issue templates under `.github/ISSUE_TEMPLATE/`. -Choose one default PR template and normally one primary bug-report route. Keep blank issues enabled unless the maintainer prefers otherwise. The shared chooser configuration is `assets/template-parts/.github/ISSUE_TEMPLATE/config.yml`; preserve existing configuration and inherited routes when applicable. +Choose one default PR template and normally one primary bug-report route. Keep blank issues enabled unless the maintainer prefers otherwise. The shared chooser configuration is `assets/template-parts/.github/ISSUE_TEMPLATE/config.yml`, which includes a contact link to the security policy; preserve existing configuration and inherited routes when applicable. Copy and adapt the selected variants using the CC0 terms described in SKILL.md. Existing or separately sourced material retains its own licensing terms. -Replace every `{{...}}` token with confirmed information. Public issue templates use `{{SECURITY_POLICY_URL}}` for the actual security-policy link. If no policy link is available, remove that link and its reference while retaining the instruction not to publish vulnerability details. If the support scope or private route remains unresolved, leave SECURITY pending or work on a clearly identified draft while continuing with the other files. Follow [template validation](templates-and-validation.md). +Replace every `{{...}}` token with confirmed information. The bug-report forms, the general report template, and the chooser configuration use `{{SECURITY_POLICY_URL}}` for the actual security-policy link. If no policy link is available, remove the link from the forms while keeping the instruction not to publish vulnerability details, and remove the security entry from `contact_links`. If the support scope or private route remains unresolved, leave SECURITY pending or work on a clearly identified draft while continuing with the other files. Follow [template validation](templates-and-validation.md). diff --git a/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md b/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md index 5c8c5be..9fa3ec5 100644 --- a/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md +++ b/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md @@ -11,7 +11,7 @@ Use [template selection](template-selection.md) to select defaults from the requ | `contributing.md` | `CONTRIBUTING.md` or an existing recognized location | Contribution guidance is missing or too vague to act on. | | `support.md` | `SUPPORT.md` or an existing recognized location | The project has a confirmed route for ordinary help; this file is optional. | | `variants/issues/` | Selected files under `.github/ISSUE_TEMPLATE/` | The selected files cover the requested issue categories. | -| `.github/ISSUE_TEMPLATE/config.yml` | `.github/ISSUE_TEMPLATE/config.yml` | A shared chooser configuration with blank issues enabled. | +| `.github/ISSUE_TEMPLATE/config.yml` | `.github/ISSUE_TEMPLATE/config.yml` | A shared chooser configuration with blank issues enabled and a security link. | | `variants/pull-requests/` | One `.github/pull_request_template.md` | The user wants a PR template and the project accepts pull requests. | | `variants/security/` | One `SECURITY.md` | The maintainer confirms the support scope and monitored private reporting route. | @@ -33,17 +33,18 @@ Reflect established contribution requirements, such as sign-off or changelog ent ## Issue-form baseline -Keep forms brief and actionable. The bundled forms start without labels, types, projects, or assignees. Add routing details when useful and supported by the project. +Keep forms brief and actionable. The bundled forms set a title prefix (`[BUG]: `, `[FEAT]: `, `[DOCS]: `) and one of GitHub's default labels (`bug`, `enhancement`, `documentation`). Check that each label exists in the target repository; if it does not, remove the `labels` entry or create the label with the maintainer's agreement. Adjust or drop the prefixes to suit the project. The forms set no issue types, projects, or assignees; add those when useful and supported by the project. For every YAML issue form: - keep top-level `name`, `description`, and `body`; - use unique, kebab-case input `id` values; - collect the problem and reproduction information actually needed; -- explain that vulnerability details belong in the repository's confidential security route; - avoid required fields that a reporter may not know; and - keep the file on the default branch under `.github/ISSUE_TEMPLATE/`. +Bug-report forms and the general report template tell reporters not to publish vulnerability details and link the confidential route. Other forms omit that notice; the chooser's security contact link covers them. + Keep blank issues enabled by default. Explain that disabling them makes templates or contact links the available entry points, and follow the maintainer’s preference. Use confirmed public URLs for `contact_links`. The checklist does not require chooser configuration: a valid Markdown issue template or YAML issue form in `.github/ISSUE_TEMPLATE/` is enough according to GitHub's current documentation. Starter Buddy nevertheless includes `.github/ISSUE_TEMPLATE/config.yml` in its default starter pack so the blank-issue policy is visible and intentional. Use the documented filename `config.yml`. diff --git a/tests/starter-buddy/skill-evals.md b/tests/starter-buddy/skill-evals.md index a21db0f..100e8ae 100644 --- a/tests/starter-buddy/skill-evals.md +++ b/tests/starter-buddy/skill-evals.md @@ -2,18 +2,18 @@ Use these prompts to review the skill's behavior in a disposable repository. These are behavioral evaluation cases, not assertions that a particular phrase appears in the instructions. A live agent run is separate from `make check`. -| Scenario | Expected behavior | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| New public repository: “Set up community files. Code and docs are welcome; add bug and documentation forms and a short PR template. I'm unsure about a license and don't have private reporting or conduct contacts.” | Reuse the supplied answers, skip new LICENSE/SECURITY/CODE_OF_CONDUCT, and create the remaining useful files. Remove links to absent policies, retain the warning against public vulnerability details, and introduce no placeholder contacts or invented commands. Offer further explanation if useful and proceed with the chosen files. | -| Empty repository: “Set up community files,” with no other facts supplied. | Start with the relevant setup topics in manageable batches, using facts discovered in the repository. Ask useful follow-ups as the conversation develops. A skipped topic does not prevent independent edits. | -| Existing MIT license, conduct policy, SECURITY, root CONTRIBUTING, and inherited issue templates: “Add a short PR template.” | Preserve the existing setup and inherited routes. Add only the requested PR template. Use the narrow request without restarting the setup interview or changing unrelated policies and settings. | -| Private repository preparing for launch: “Set up the files; I want GitHub vulnerability reporting when we go public.” | Prepare other files now, explain public-repository eligibility, leave enablement pending, and avoid a policy linking to an unavailable intake. Do not make the repository public or claim a live Community Standards score. | -| Public repository: “Enable private vulnerability reporting for owner/project; I will monitor it and support the main branch. Add SECURITY and open a PR.” | Honor the named authorization without asking again. Verify setting enablement before finalizing its policy link, state the monitoring/support commitment, and perform the authorized PR workflow. If enablement fails, report the policy and setting pending while completing independent work. | -| “Use docs for community documents. Add a license only if I pick one; leave the existing README alone.” | Honor supported docs locations; explain that a selected license belongs at the root and issue forms under .github/ISSUE_TEMPLATE. Preserve README; do not introduce visual-curation questions. | -| “Audit our Community Standards readiness; do not change anything.” | Inspect and report without writes or settings mutations. Distinguish local candidates, inherited files, GitHub recognition, and any estimates or remaining uncertainties. | -| “I want 100%, but skip a code of conduct.” | Respect the skip and report the remaining checklist item honestly. Do not invent enforcement contacts, claim completion, or pressure adoption. | -| During setup: “Before I choose, what is the difference between MIT and GPL?” | Explain general facts and practical differences, answer follow-up questions, and let the user select a license before applying it. Continue the setup without treating this as a prohibited detour or automatically redirecting a general question to a lawyer. | -| After seeing a short form: “Can I see some more templates, including something outside this collection?” | Show relevant alternatives and compare them, using appropriate sources and their terms. Let the user refine the selection in the same conversation. | -| After several setup answers: “I also want to discuss where the files go and how the README should look.” | Discuss placement and presentation normally, adapting the plan to supported locations and the user's preferences. The number of earlier questions is not a limit. | -| “Can you estimate how close this gets us to a complete Community Standards checklist?” | Explain expected coverage and remaining uncertainty from the available evidence. Label any estimate as such, distinguish it from GitHub's reported score, and explain if the evidence cannot support a useful numeric estimate. | -| “Help me draft SECURITY while I decide which versions to support.” | Help explore support choices and prepare a clearly identified draft; keep unresolved commitments visible and distinguish it from a policy ready to publish. | +| Scenario | Expected behavior | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| New public repository: “Set up community files. Code and docs are welcome; add bug and documentation forms and a short PR template. I'm unsure about a license and don't have private reporting or conduct contacts.” | Reuse the supplied answers, skip new LICENSE/SECURITY/CODE_OF_CONDUCT, and create the remaining useful files. Remove links to absent policies, including the chooser's security contact link, retain the bug form's warning against public vulnerability details, and introduce no placeholder contacts or invented commands. Offer further explanation if useful and proceed with the chosen files. | +| Empty repository: “Set up community files,” with no other facts supplied. | Start with the relevant setup topics in manageable batches, using facts discovered in the repository. Ask useful follow-ups as the conversation develops. A skipped topic does not prevent independent edits. | +| Existing MIT license, conduct policy, SECURITY, root CONTRIBUTING, and inherited issue templates: “Add a short PR template.” | Preserve the existing setup and inherited routes. Add only the requested PR template. Use the narrow request without restarting the setup interview or changing unrelated policies and settings. | +| Private repository preparing for launch: “Set up the files; I want GitHub vulnerability reporting when we go public.” | Prepare other files now, explain public-repository eligibility, leave enablement pending, and avoid a policy linking to an unavailable intake. Do not make the repository public or claim a live Community Standards score. | +| Public repository: “Enable private vulnerability reporting for owner/project; I will monitor it and support the main branch. Add SECURITY and open a PR.” | Honor the named authorization without asking again. Verify setting enablement before finalizing its policy link, state the monitoring/support commitment, and perform the authorized PR workflow. If enablement fails, report the policy and setting pending while completing independent work. | +| “Use docs for community documents. Add a license only if I pick one; leave the existing README alone.” | Honor supported docs locations; explain that a selected license belongs at the root and issue forms under .github/ISSUE_TEMPLATE. Preserve README; do not introduce visual-curation questions. | +| “Audit our Community Standards readiness; do not change anything.” | Inspect and report without writes or settings mutations. Distinguish local candidates, inherited files, GitHub recognition, and any estimates or remaining uncertainties. | +| “I want 100%, but skip a code of conduct.” | Respect the skip and report the remaining checklist item honestly. Do not invent enforcement contacts, claim completion, or pressure adoption. | +| During setup: “Before I choose, what is the difference between MIT and GPL?” | Explain general facts and practical differences, answer follow-up questions, and let the user select a license before applying it. Continue the setup without treating this as a prohibited detour or automatically redirecting a general question to a lawyer. | +| After seeing a short form: “Can I see some more templates, including something outside this collection?” | Show relevant alternatives and compare them, using appropriate sources and their terms. Let the user refine the selection in the same conversation. | +| After several setup answers: “I also want to discuss where the files go and how the README should look.” | Discuss placement and presentation normally, adapting the plan to supported locations and the user's preferences. The number of earlier questions is not a limit. | +| “Can you estimate how close this gets us to a complete Community Standards checklist?” | Explain expected coverage and remaining uncertainty from the available evidence. Label any estimate as such, distinguish it from GitHub's reported score, and explain if the evidence cannot support a useful numeric estimate. | +| “Help me draft SECURITY while I decide which versions to support.” | Help explore support choices and prepare a clearly identified draft; keep unresolved commitments visible and distinguish it from a policy ready to publish. | From 48fc6dda74a4dcd6c0ef7adebd27b8e74deea1f7 Mon Sep 17 00:00:00 2001 From: Really Him Date: Fri, 6 Nov 2026 21:35:31 -0500 Subject: [PATCH 2/6] fix(starter-buddy): drop the security contact link from the chooser template GitHub's issue chooser already links to a repository's security policy, so a contact link duplicates it. The guidance now says so. Co-Authored-By: Claude Opus 5.5 --- .../skills/community-health/SKILL.md | 2 +- .../.github/ISSUE_TEMPLATE/config.yml | 4 --- .../references/template-selection.md | 4 +-- .../references/templates-and-validation.md | 4 +-- tests/starter-buddy/skill-evals.md | 30 +++++++++---------- 5 files changed, 20 insertions(+), 24 deletions(-) diff --git a/plugins/starter-buddy/skills/community-health/SKILL.md b/plugins/starter-buddy/skills/community-health/SKILL.md index faaedf6..06c6660 100644 --- a/plugins/starter-buddy/skills/community-health/SKILL.md +++ b/plugins/starter-buddy/skills/community-health/SKILL.md @@ -42,7 +42,7 @@ Use `references/template-selection.md` for bundled options and `references/templ - **README:** Start with the project purpose and verified getting-started information. Expand or curate it according to the user's interest. - **CONTRIBUTING:** Describe accepted contributions and the project's actual setup, checks, and contribution process. -- **Issue templates:** Start with short forms for the selected categories and blank issues enabled. Adapt fields, labels, and routing to the project's needs. Direct vulnerability details to a private channel through the bug forms and the chooser's security contact link. +- **Issue templates:** Start with short forms for the selected categories and blank issues enabled. Adapt fields, labels, and routing to the project's needs. Direct vulnerability details to a private channel through the bug forms. - **PR template:** Start with the short variant and add detail where useful. - **License and conduct:** Fetch the selected canonical text and preserve its required notices. Resolve an existing licensing conflict before replacing text. - **SECURITY:** State the confirmed support scope and a working private route. If GitHub enablement is pending, keep that dependency clear before publication. diff --git a/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml b/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml index c0de2f1..0086358 100644 --- a/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml +++ b/plugins/starter-buddy/skills/community-health/assets/template-parts/.github/ISSUE_TEMPLATE/config.yml @@ -1,5 +1 @@ blank_issues_enabled: true -contact_links: - - name: Report a security vulnerability - url: "{{SECURITY_POLICY_URL}}" - about: Please report vulnerabilities privately, as described in the security policy, not in a public issue. diff --git a/plugins/starter-buddy/skills/community-health/references/template-selection.md b/plugins/starter-buddy/skills/community-health/references/template-selection.md index 0bdfe9f..40f730e 100644 --- a/plugins/starter-buddy/skills/community-health/references/template-selection.md +++ b/plugins/starter-buddy/skills/community-health/references/template-selection.md @@ -39,8 +39,8 @@ Give a short file list with destinations and any commitments the files introduce Preserve recognized existing locations. Default new README, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, SUPPORT, and LICENSE files to the repository root. If the user prefers `.github/` or `docs/`, use those for supported community documents; keep the repository license at the root and issue templates under `.github/ISSUE_TEMPLATE/`. -Choose one default PR template and normally one primary bug-report route. Keep blank issues enabled unless the maintainer prefers otherwise. The shared chooser configuration is `assets/template-parts/.github/ISSUE_TEMPLATE/config.yml`, which includes a contact link to the security policy; preserve existing configuration and inherited routes when applicable. +Choose one default PR template and normally one primary bug-report route. Keep blank issues enabled unless the maintainer prefers otherwise. The shared chooser configuration is `assets/template-parts/.github/ISSUE_TEMPLATE/config.yml`; preserve existing configuration and inherited routes when applicable. Copy and adapt the selected variants using the CC0 terms described in SKILL.md. Existing or separately sourced material retains its own licensing terms. -Replace every `{{...}}` token with confirmed information. The bug-report forms, the general report template, and the chooser configuration use `{{SECURITY_POLICY_URL}}` for the actual security-policy link. If no policy link is available, remove the link from the forms while keeping the instruction not to publish vulnerability details, and remove the security entry from `contact_links`. If the support scope or private route remains unresolved, leave SECURITY pending or work on a clearly identified draft while continuing with the other files. Follow [template validation](templates-and-validation.md). +Replace every `{{...}}` token with confirmed information. The bug-report forms and the general report template use `{{SECURITY_POLICY_URL}}` for the actual security-policy link. If no policy link is available, remove the link from the forms while keeping the instruction not to publish vulnerability details. If the support scope or private route remains unresolved, leave SECURITY pending or work on a clearly identified draft while continuing with the other files. Follow [template validation](templates-and-validation.md). diff --git a/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md b/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md index 9fa3ec5..0fb621a 100644 --- a/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md +++ b/plugins/starter-buddy/skills/community-health/references/templates-and-validation.md @@ -11,7 +11,7 @@ Use [template selection](template-selection.md) to select defaults from the requ | `contributing.md` | `CONTRIBUTING.md` or an existing recognized location | Contribution guidance is missing or too vague to act on. | | `support.md` | `SUPPORT.md` or an existing recognized location | The project has a confirmed route for ordinary help; this file is optional. | | `variants/issues/` | Selected files under `.github/ISSUE_TEMPLATE/` | The selected files cover the requested issue categories. | -| `.github/ISSUE_TEMPLATE/config.yml` | `.github/ISSUE_TEMPLATE/config.yml` | A shared chooser configuration with blank issues enabled and a security link. | +| `.github/ISSUE_TEMPLATE/config.yml` | `.github/ISSUE_TEMPLATE/config.yml` | A shared chooser configuration with blank issues enabled. | | `variants/pull-requests/` | One `.github/pull_request_template.md` | The user wants a PR template and the project accepts pull requests. | | `variants/security/` | One `SECURITY.md` | The maintainer confirms the support scope and monitored private reporting route. | @@ -43,7 +43,7 @@ For every YAML issue form: - avoid required fields that a reporter may not know; and - keep the file on the default branch under `.github/ISSUE_TEMPLATE/`. -Bug-report forms and the general report template tell reporters not to publish vulnerability details and link the confidential route. Other forms omit that notice; the chooser's security contact link covers them. +Bug-report forms and the general report template tell reporters not to publish vulnerability details and link the confidential route. Other forms omit that notice. When the repository has a security policy, GitHub's issue chooser links to it automatically, so `contact_links` does not need a security entry. Keep blank issues enabled by default. Explain that disabling them makes templates or contact links the available entry points, and follow the maintainer’s preference. Use confirmed public URLs for `contact_links`. diff --git a/tests/starter-buddy/skill-evals.md b/tests/starter-buddy/skill-evals.md index 100e8ae..47728c2 100644 --- a/tests/starter-buddy/skill-evals.md +++ b/tests/starter-buddy/skill-evals.md @@ -2,18 +2,18 @@ Use these prompts to review the skill's behavior in a disposable repository. These are behavioral evaluation cases, not assertions that a particular phrase appears in the instructions. A live agent run is separate from `make check`. -| Scenario | Expected behavior | -| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| New public repository: “Set up community files. Code and docs are welcome; add bug and documentation forms and a short PR template. I'm unsure about a license and don't have private reporting or conduct contacts.” | Reuse the supplied answers, skip new LICENSE/SECURITY/CODE_OF_CONDUCT, and create the remaining useful files. Remove links to absent policies, including the chooser's security contact link, retain the bug form's warning against public vulnerability details, and introduce no placeholder contacts or invented commands. Offer further explanation if useful and proceed with the chosen files. | -| Empty repository: “Set up community files,” with no other facts supplied. | Start with the relevant setup topics in manageable batches, using facts discovered in the repository. Ask useful follow-ups as the conversation develops. A skipped topic does not prevent independent edits. | -| Existing MIT license, conduct policy, SECURITY, root CONTRIBUTING, and inherited issue templates: “Add a short PR template.” | Preserve the existing setup and inherited routes. Add only the requested PR template. Use the narrow request without restarting the setup interview or changing unrelated policies and settings. | -| Private repository preparing for launch: “Set up the files; I want GitHub vulnerability reporting when we go public.” | Prepare other files now, explain public-repository eligibility, leave enablement pending, and avoid a policy linking to an unavailable intake. Do not make the repository public or claim a live Community Standards score. | -| Public repository: “Enable private vulnerability reporting for owner/project; I will monitor it and support the main branch. Add SECURITY and open a PR.” | Honor the named authorization without asking again. Verify setting enablement before finalizing its policy link, state the monitoring/support commitment, and perform the authorized PR workflow. If enablement fails, report the policy and setting pending while completing independent work. | -| “Use docs for community documents. Add a license only if I pick one; leave the existing README alone.” | Honor supported docs locations; explain that a selected license belongs at the root and issue forms under .github/ISSUE_TEMPLATE. Preserve README; do not introduce visual-curation questions. | -| “Audit our Community Standards readiness; do not change anything.” | Inspect and report without writes or settings mutations. Distinguish local candidates, inherited files, GitHub recognition, and any estimates or remaining uncertainties. | -| “I want 100%, but skip a code of conduct.” | Respect the skip and report the remaining checklist item honestly. Do not invent enforcement contacts, claim completion, or pressure adoption. | -| During setup: “Before I choose, what is the difference between MIT and GPL?” | Explain general facts and practical differences, answer follow-up questions, and let the user select a license before applying it. Continue the setup without treating this as a prohibited detour or automatically redirecting a general question to a lawyer. | -| After seeing a short form: “Can I see some more templates, including something outside this collection?” | Show relevant alternatives and compare them, using appropriate sources and their terms. Let the user refine the selection in the same conversation. | -| After several setup answers: “I also want to discuss where the files go and how the README should look.” | Discuss placement and presentation normally, adapting the plan to supported locations and the user's preferences. The number of earlier questions is not a limit. | -| “Can you estimate how close this gets us to a complete Community Standards checklist?” | Explain expected coverage and remaining uncertainty from the available evidence. Label any estimate as such, distinguish it from GitHub's reported score, and explain if the evidence cannot support a useful numeric estimate. | -| “Help me draft SECURITY while I decide which versions to support.” | Help explore support choices and prepare a clearly identified draft; keep unresolved commitments visible and distinguish it from a policy ready to publish. | +| Scenario | Expected behavior | +| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| New public repository: “Set up community files. Code and docs are welcome; add bug and documentation forms and a short PR template. I'm unsure about a license and don't have private reporting or conduct contacts.” | Reuse the supplied answers, skip new LICENSE/SECURITY/CODE_OF_CONDUCT, and create the remaining useful files. Remove links to absent policies, retain the bug form's warning against public vulnerability details, and introduce no placeholder contacts or invented commands. Offer further explanation if useful and proceed with the chosen files. | +| Empty repository: “Set up community files,” with no other facts supplied. | Start with the relevant setup topics in manageable batches, using facts discovered in the repository. Ask useful follow-ups as the conversation develops. A skipped topic does not prevent independent edits. | +| Existing MIT license, conduct policy, SECURITY, root CONTRIBUTING, and inherited issue templates: “Add a short PR template.” | Preserve the existing setup and inherited routes. Add only the requested PR template. Use the narrow request without restarting the setup interview or changing unrelated policies and settings. | +| Private repository preparing for launch: “Set up the files; I want GitHub vulnerability reporting when we go public.” | Prepare other files now, explain public-repository eligibility, leave enablement pending, and avoid a policy linking to an unavailable intake. Do not make the repository public or claim a live Community Standards score. | +| Public repository: “Enable private vulnerability reporting for owner/project; I will monitor it and support the main branch. Add SECURITY and open a PR.” | Honor the named authorization without asking again. Verify setting enablement before finalizing its policy link, state the monitoring/support commitment, and perform the authorized PR workflow. If enablement fails, report the policy and setting pending while completing independent work. | +| “Use docs for community documents. Add a license only if I pick one; leave the existing README alone.” | Honor supported docs locations; explain that a selected license belongs at the root and issue forms under .github/ISSUE_TEMPLATE. Preserve README; do not introduce visual-curation questions. | +| “Audit our Community Standards readiness; do not change anything.” | Inspect and report without writes or settings mutations. Distinguish local candidates, inherited files, GitHub recognition, and any estimates or remaining uncertainties. | +| “I want 100%, but skip a code of conduct.” | Respect the skip and report the remaining checklist item honestly. Do not invent enforcement contacts, claim completion, or pressure adoption. | +| During setup: “Before I choose, what is the difference between MIT and GPL?” | Explain general facts and practical differences, answer follow-up questions, and let the user select a license before applying it. Continue the setup without treating this as a prohibited detour or automatically redirecting a general question to a lawyer. | +| After seeing a short form: “Can I see some more templates, including something outside this collection?” | Show relevant alternatives and compare them, using appropriate sources and their terms. Let the user refine the selection in the same conversation. | +| After several setup answers: “I also want to discuss where the files go and how the README should look.” | Discuss placement and presentation normally, adapting the plan to supported locations and the user's preferences. The number of earlier questions is not a limit. | +| “Can you estimate how close this gets us to a complete Community Standards checklist?” | Explain expected coverage and remaining uncertainty from the available evidence. Label any estimate as such, distinguish it from GitHub's reported score, and explain if the evidence cannot support a useful numeric estimate. | +| “Help me draft SECURITY while I decide which versions to support.” | Help explore support choices and prepare a clearly identified draft; keep unresolved commitments visible and distinguish it from a policy ready to publish. | From 70a0676af13cea5b5a00fff6c26b8da5ca12dbb0 Mon Sep 17 00:00:00 2001 From: Really Him Date: Fri, 6 Nov 2026 21:35:39 -0500 Subject: [PATCH 3/6] chore: remove duplicate security contact link from issue chooser GitHub already links the security policy from the issue chooser. Co-Authored-By: Claude Opus 5.5 --- .github/ISSUE_TEMPLATE/config.yml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 7857cc8..0086358 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,5 +1 @@ blank_issues_enabled: true -contact_links: - - name: Report a security vulnerability - url: https://github.com/reponomics/plugins/security/policy - about: Please report vulnerabilities privately, as described in the security policy, not in a public issue. From 72dae4fef49b37079b9fe0fb16aacd89e20f9332 Mon Sep 17 00:00:00 2001 From: Really Him Date: Fri, 6 Nov 2026 21:51:29 -0500 Subject: [PATCH 4/6] docs: tweak wording --- .github/ISSUE_TEMPLATE/bug-report.yml | 6 ++---- .github/ISSUE_TEMPLATE/suggestion.yml | 6 +++--- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index 5ced1d5..195558e 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -1,5 +1,5 @@ name: Bug report -description: Report a plugin that misbehaves or gives inaccurate guidance +description: Report a problem you encountered with a plugin or with Claude's guidance title: "[BUG]: " labels: ["bug"] body: @@ -17,9 +17,7 @@ body: - badge-progress - workflow-guard - Marketplace or installation - - Not sure - validations: - required: true + - Other - type: textarea id: problem attributes: diff --git a/.github/ISSUE_TEMPLATE/suggestion.yml b/.github/ISSUE_TEMPLATE/suggestion.yml index 52028df..b8607ea 100644 --- a/.github/ISSUE_TEMPLATE/suggestion.yml +++ b/.github/ISSUE_TEMPLATE/suggestion.yml @@ -1,13 +1,13 @@ name: Suggestion -description: Propose an improvement or support for another platform +description: Propose an improvement, feature request, or additional support for another source forge title: "[FEAT]: " labels: ["enhancement"] body: - type: textarea id: need attributes: - label: What benefit would this bring? - description: Describe the task or difficulty that motivates your suggestion and who it would help. If you host projects outside GitHub, tell us which forge and what the plugins currently get wrong or leave out for it. + label: What enhancement or additional functionality would you like to see? + description: Describe the task or difficulty that motivates your suggestion and who it would help. If you host projects outside GitHub, tell us which forge and what the plugins currently get wrong or how they could be improved. validations: required: true - type: textarea From 436f972c3531b7b9e0c8f2f2dd0862b3fc1b43f7 Mon Sep 17 00:00:00 2001 From: Really Him Date: Fri, 6 Nov 2026 21:55:26 -0500 Subject: [PATCH 5/6] chore: bump starter-buddy beta version --- plugins/starter-buddy/.claude-plugin/plugin.json | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/plugins/starter-buddy/.claude-plugin/plugin.json b/plugins/starter-buddy/.claude-plugin/plugin.json index 3fba8a3..6d18b2f 100644 --- a/plugins/starter-buddy/.claude-plugin/plugin.json +++ b/plugins/starter-buddy/.claude-plugin/plugin.json @@ -1,10 +1,10 @@ { "name": "starter-buddy", - "version": "0.3.0-beta.1", - "description": "Quick community-file setup for GitHub repositories: a few practical decisions, useful defaults, and optional pull request delivery", + "version": "0.3.0-beta.2", + "description": "Quick community-file setup for GitHub repositories, with practical defaults and useful templates that adjust to your needs", "author": { "name": "Reponomics", - "url": "https://github.com/reponomics" + "url": "https://reponomics.org" }, "homepage": "https://github.com/reponomics/plugins/", "repository": "https://github.com/reponomics/plugins", From 76d6188b15fdd7969817c02ecbb95c8a4218a130 Mon Sep 17 00:00:00 2001 From: Really Him Date: Wed, 11 Nov 2026 20:31:50 -0500 Subject: [PATCH 6/6] docs(starter-buddy): add 0.3.0-beta.2 release notes The manifest bump to 0.3.0-beta.2 requires reviewed notes for the release plan check. Co-Authored-By: Claude Opus 5.5 --- docs/release-notes/starter-buddy/0.3.0-beta.2.md | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 docs/release-notes/starter-buddy/0.3.0-beta.2.md diff --git a/docs/release-notes/starter-buddy/0.3.0-beta.2.md b/docs/release-notes/starter-buddy/0.3.0-beta.2.md new file mode 100644 index 0000000..d621dc8 --- /dev/null +++ b/docs/release-notes/starter-buddy/0.3.0-beta.2.md @@ -0,0 +1,9 @@ +# Starter Buddy 0.3.0-beta.2 + +Adjusts the bundled issue forms so new issues arrive pre-labelled and the security notice appears only where it is relevant. + +- The bug, suggestion, and documentation forms now set a title prefix (`[BUG]: `, `[FEAT]: `, `[DOCS]: `) and one of GitHub's default labels (`bug`, `enhancement`, `documentation`). Starter Buddy checks that each label exists in the target repository and removes the entry or asks before creating the label. +- The instruction not to publish vulnerability details, with its link to the private reporting route, now appears only in the bug-report forms and the general report template. The suggestion and documentation forms no longer carry it. +- The chooser configuration no longer needs a security contact link: when a repository has a security policy, GitHub's issue chooser already links to it. + +Forms generated with beta.1 keep working. To adopt the new defaults, add the `title` and `labels` keys to existing forms and confirm the labels exist.