@cyanheads/mcp-ts-core 0.13.3 → 0.13.4

package/templates/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -76,7 +76,7 @@ body:
     id: description
     attributes:
       label: Description
-      description: What happened and what you expected instead.
+      description: What happened and what you expected instead — two or three sentences.
     validations:
       required: true
 
@@ -112,6 +112,6 @@ body:
     id: context
     attributes:
       label: Additional context
-      description: Workarounds, related issues, logs, or anything else relevant.
+      description: Only what changes the fix — a workaround, a related issue, the one log line that matters.
     validations:
       required: false

package/templates/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -17,7 +17,7 @@ body:
     id: use-case
     attributes:
       label: Use case
-      description: What problem does this solve? Who benefits?
+      description: What problem does this solve? Who benefits? Two or three sentences.
     validations:
       required: true
 
@@ -42,6 +42,6 @@ body:
     id: context
     attributes:
       label: Additional context
-      description: Related issues, prior art, links, or anything else relevant.
+      description: Only what the reader needs to act — related issues, prior art, a link.
     validations:
       required: false

package/templates/changelog/template.md

@@ -6,8 +6,8 @@
 
 # Required. One-line GitHub Release-style headline. 350 character cap — a
 # ceiling, not a target. Default short and scannable. Don't pad, don't stitch
-# unrelated changes with commas/semicolons into an inventory — pick the
-# headline, like a tag's theme line. Quotes required: unquoted YAML treats
+# unrelated changes with commas/semicolons into an inventory — pick the one
+# headline the release is about. Quotes required: unquoted YAML treats
 # `: ` inside the value as a key separator and fails GitHub's strict parser.
 summary: ""
 
@@ -119,11 +119,11 @@ security: false
   TAG ANNOTATIONS — the annotated tag body renders as the GitHub Release body
   via `gh release create --notes-from-tag`. It is a condensed digest of this
   entry, never a copy, and its format is owned by the `release-and-publish`
-  skill (step 4, "Create the annotated tag"): the entry's `summary:` as the
-  theme line without the version, flat headline bullets — no Keep-a-Changelog
-  section headers, no gates line — at most one deps line, issue backlinks,
-  and the changelog link last. In release-PR mode the `git-wrapup` skill
-  authors that digest as the PR body's `## Changes` and the tag copies it.
+  skill (step 4, "Create the annotated tag"): a short subject line without the
+  version, flat headline bullets — no Keep-a-Changelog section headers, no
+  gates line — at most one deps line, issue backlinks, and the changelog link
+  last. In release-PR mode the `git-wrapup` skill authors those bullets as the
+  PR body's `## Changes` and the tag copies them.
 -->
 
 ## Added