diff --git a/.github/ISSUE_TEMPLATE/1-documentation_change.yml b/.github/ISSUE_TEMPLATE/1-documentation_change.yml
index 66badf63e..492d7a066 100644
--- a/.github/ISSUE_TEMPLATE/1-documentation_change.yml
+++ b/.github/ISSUE_TEMPLATE/1-documentation_change.yml
@@ -1,6 +1,6 @@
 name: Report Docs Issue
 description: Suggest an addition or modification to the documentation
-labels: ["type: documentation"]
+labels: [triage]
 body:
   - type: dropdown
     attributes:
diff --git a/.github/ISSUE_TEMPLATE/2-feature_request.yml b/.github/ISSUE_TEMPLATE/2-feature_request.yml
index b4d243b24..f82abefa1 100644
--- a/.github/ISSUE_TEMPLATE/2-feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/2-feature_request.yml
@@ -1,6 +1,6 @@
 name: Feature request
 description: Request a new feature
-labels: ["type: feature"]
+labels: [triage]
 body:
   - type: checkboxes
     attributes:
diff --git a/.github/ISSUE_TEMPLATE/3-bug_report.yml b/.github/ISSUE_TEMPLATE/3-bug_report.yml
index 2cdeccb6f..79276f58a 100644
--- a/.github/ISSUE_TEMPLATE/3-bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/3-bug_report.yml
@@ -1,5 +1,6 @@
 name: Bug report
 description: Report an issue with shadcn-svelte
+labels: [triage]
 body:
   - type: markdown
     attributes:
@@ -24,7 +25,7 @@ body:
     attributes:
       label: Reproduction
       description: |
-        Provide a minimal reproduction of the problem. Include a StackBlitz or link to a GitHub repository that we can easily run to recreate the issue. If a report is vague and does not have a reproduction, it will be closed without warning. 
+        Provide a minimal reproduction of the problem. Include a StackBlitz or link to a GitHub repository that we can easily run to recreate the issue. If a report is vague and does not have a reproduction, it will be closed without warning.
 
         To get started, you can use the following StackBlitz template:
         https://shadcn-svelte.com/repro
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 81420086b..45a934e4b 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,6 +1,8 @@
+<!--
 ### Before submitting the PR, please make sure you do the following
 
 - If your PR isn't addressing a small fix (like a typo), it references an issue where it is discussed ahead of time and assigned to you. In many cases, features are absent for a reason.
 - Prefix your PR title with `feat:`, `fix:`, `chore:`, or `docs:`.
 - This message body should clearly illustrate what problems it solves.
 - Format & lint the code with `pnpm format` and `pnpm lint`
+-->
diff --git a/.github/workflows/reproduire-close.yml b/.github/workflows/reproduire-close.yml
index 9c99678c6..02fbd03c7 100644
--- a/.github/workflows/reproduire-close.yml
+++ b/.github/workflows/reproduire-close.yml
@@ -14,8 +14,8 @@ jobs:
       - uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9.0.0
         with:
           days-before-stale: -1 # Issues and PR will never be flagged stale automatically.
-          stale-issue-label: "status: needs reproduction" # Label that flags an issue as stale.
-          only-labels: "status: needs reproduction" # Only process these issues
+          stale-issue-label: needs reproduction # Label that flags an issue as stale.
+          only-labels: needs reproduction # Only process these issues
           days-before-issue-close: 7
           ignore-updates: true
           remove-stale-when-updated: false
diff --git a/.github/workflows/reproduire.yml b/.github/workflows/reproduire.yml
index b75bea220..0529b24c6 100644
--- a/.github/workflows/reproduire.yml
+++ b/.github/workflows/reproduire.yml
@@ -13,4 +13,4 @@ jobs:
       - uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
       - uses: Hebilicious/reproduire@4b686ae9cbb72dad60f001d278b6e3b2ce40a9ac # v0.0.9-mp
         with:
-          label: "status: needs reproduction"
+          label: needs reproduction