@openhands/extensions 0.17.0 → 0.19.0

package/automations/catalog/github-agents-md-maintainer/manifest.json

@@ -0,0 +1,101 @@
+{
+  "id": "github-agents-md-maintainer",
+  "name": "AGENTS.md Maintainer",
+  "category": "Documentation",
+  "icon": "bot",
+  "description": "Keep AGENTS.md current in your repositories. On a schedule, an agent reads the repository, creates or updates AGENTS.md, and opens a pull request - and stays quiet while one of its pull requests is still open.",
+  "requires": {
+    "integrations": {
+      "github": {
+        "message": "Used to read the repository, push the branch, and open the pull request."
+      }
+    },
+    "features": [
+      "customTarball"
+    ]
+  },
+  "popularityRank": 80,
+  "estimatedSetupMinutes": 3,
+  "exampleImplementation": "Trigger: cron, weekly by default (0 9 * * 1)\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN, with permission to write contents and pull requests\n\n1. Read the repositories, branch prefix, pull request mode, and schedule from setup.\n2. Process each repository independently, with its own state, so one falling behind never blocks another.\n3. Key one unit of work to the ISO week, so a cron that fires more often, a retried run, or a restarted service cannot open the same pull request twice.\n4. Skip a repository whose previous pull request from this automation is still open; a second one would edit the same file.\n5. Ask GitHub whether AGENTS.md exists, which decides create vs update and the pull request title.\n6. Clone the default branch into a directory of its own, create the working branch, and start an OpenHands conversation with that directory as its workspace.\n7. The agent reads the repository, edits AGENTS.md, commits, pushes, and opens the pull request; the script verifies that on GitHub and opens it itself when the agent did not.\n8. Record no-changes when AGENTS.md is already accurate, which is the expected result most weeks.\n9. Remove the clone once the conversation has stopped.",
+  "impact": {
+    "basis": "completed-runs",
+    "one": "1 maintenance pass completed",
+    "other": "{{count}} maintenance passes completed"
+  },
+  "setup": {
+    "version": "1.0",
+    "mode": "direct",
+    "form": {
+      "triggers": {
+        "cron": {
+          "schedule": {
+            "type": "cron",
+            "label": "Check frequency",
+            "help": "How often to review AGENTS.md. Work is keyed by ISO week, so a schedule more frequent than weekly only polls.",
+            "default": "0 9 * * 1",
+            "required": true
+          },
+          "timezone": {
+            "type": "timezone",
+            "label": "Timezone",
+            "help": "Timezone the schedule is interpreted in.",
+            "default": "UTC",
+            "required": true
+          }
+        }
+      },
+      "args": {
+        "repositories": {
+          "type": "repo-picker",
+          "label": "Repositories",
+          "help": "The repositories whose AGENTS.md is maintained. Each keeps its own state and its own weekly claim.",
+          "provider": "github",
+          "multiple": true,
+          "required": true
+        },
+        "branchPrefix": {
+          "type": "text",
+          "label": "Branch prefix",
+          "help": "Branches are named after this prefix and the ISO week, such as openhands/agents-md-2026-W34. It is also how the automation recognises its own open pull requests.",
+          "default": "openhands/agents-md",
+          "required": true,
+          "constraints": {
+            "minLength": 1,
+            "maxLength": 50
+          }
+        },
+        "pullRequestMode": {
+          "type": "select",
+          "label": "Pull request mode",
+          "help": "Whether the pull request is opened as a draft or ready for review.",
+          "default": "draft",
+          "required": true,
+          "options": [
+            {
+              "value": "draft",
+              "label": "Draft"
+            },
+            {
+              "value": "ready",
+              "label": "Ready for review"
+            }
+          ]
+        }
+      }
+    },
+    "bundle": {
+      "version": "1.0.0",
+      "entrypoint": "python3 main.py",
+      "timeout": 900,
+      "files": {
+        "main.py": "skills/github-agents-md-maintainer/scripts/main.py"
+      },
+      "config": {
+        "repos": "{{form.repositories}}",
+        "branch_prefix": "{{form.branchPrefix}}",
+        "pull_request_mode": "{{form.pullRequestMode}}"
+      }
+    },
+    "message": "This deployment cannot run the scheduled AGENTS.md automation directly. Set it up in this conversation instead: confirm the repositories to maintain, the branch prefix, whether pull requests open as drafts, and the schedule, then create the automation."
+  }
+}

package/automations/catalog/github-issue-to-pr/manifest.json

@@ -0,0 +1,112 @@
+{
+  "id": "github-issue-to-pr",
+  "name": "GitHub Issue to PR Agent",
+  "category": "Software development",
+  "description": "Watch for a configurable label on GitHub issues, implement the issue in a clone of the default branch, and open a pull request for each label event.",
+  "requires": {
+    "integrations": {
+      "github": {
+        "message": "Used to read labelled issues, push the branch, and open the pull request."
+      }
+    },
+    "features": [
+      "customTarball"
+    ]
+  },
+  "popularityRank": 95,
+  "estimatedSetupMinutes": 4,
+  "exampleImplementation": "Trigger: cron polling for open GitHub issues with a configured label such as openhands\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN, with permission to write contents, issues, and pull requests\n\n1. Read the repositories, trigger label, branch prefix, draft mode, and polling schedule from setup.\n2. Poll each repository independently, with its own state, so issue numbers never collide.\n3. List open labelled issues, drop pull requests, and find the latest matching GitHub labeled issue event for each.\n4. Deduplicate on the label event ID so every label application queues exactly one attempt.\n5. Clone the default branch into a directory of its own, create the working branch, and start an OpenHands conversation with that directory as its workspace. The clone carries no credential and the agent is handed no secrets, because the prompt is built from an issue body that anyone can write.\n6. Comment on the issue with the branch and the conversation link.\n7. Once the conversation has stopped, commit whatever the agent left, push the branch, open a draft pull request titled after the issue, and comment the link on the issue. An agent that made no changes gets its answer posted instead.\n8. Remove the clone once the conversation has stopped, so nothing accumulates between runs.",
+  "impact": {
+    "basis": "completed-runs",
+    "one": "1 issue sweep completed",
+    "other": "{{count}} issue sweeps completed"
+  },
+  "setup": {
+    "version": "1.0",
+    "mode": "direct",
+    "form": {
+      "triggers": {
+        "cron": {
+          "schedule": {
+            "type": "cron",
+            "label": "Check frequency",
+            "help": "How often to look for newly labelled issues.",
+            "default": "*/15 * * * *",
+            "required": true
+          },
+          "timezone": {
+            "type": "timezone",
+            "label": "Timezone",
+            "help": "Timezone the schedule is interpreted in.",
+            "default": "UTC",
+            "required": true
+          }
+        }
+      },
+      "args": {
+        "repositories": {
+          "type": "repo-picker",
+          "label": "Repositories",
+          "help": "The repositories whose labelled issues are implemented. Each is polled independently and keeps its own state, so issue numbers never collide between them.",
+          "provider": "github",
+          "multiple": true,
+          "required": true
+        },
+        "triggerLabel": {
+          "type": "text",
+          "label": "Trigger label",
+          "help": "Only issues carrying this label are worked on.",
+          "default": "openhands",
+          "required": true,
+          "constraints": {
+            "minLength": 1,
+            "maxLength": 50
+          }
+        },
+        "branchPrefix": {
+          "type": "text",
+          "label": "Branch prefix",
+          "help": "Branches are named after this prefix and the issue number, such as openhands/issue-42.",
+          "default": "openhands/issue",
+          "required": true,
+          "constraints": {
+            "minLength": 1,
+            "maxLength": 50
+          }
+        },
+        "pullRequestMode": {
+          "type": "select",
+          "label": "Pull request mode",
+          "help": "Whether the pull request is opened as a draft or ready for review.",
+          "default": "draft",
+          "required": true,
+          "options": [
+            {
+              "value": "draft",
+              "label": "Draft"
+            },
+            {
+              "value": "ready",
+              "label": "Ready for review"
+            }
+          ]
+        }
+      }
+    },
+    "bundle": {
+      "version": "1.0.0",
+      "entrypoint": "python3 main.py",
+      "timeout": 900,
+      "files": {
+        "main.py": "skills/github-issue-to-pr/scripts/main.py"
+      },
+      "config": {
+        "repos": "{{form.repositories}}",
+        "trigger_label": "{{form.triggerLabel}}",
+        "branch_prefix": "{{form.branchPrefix}}",
+        "pull_request_mode": "{{form.pullRequestMode}}"
+      }
+    },
+    "message": "This deployment cannot run the scheduled issue-to-PR automation directly. Set it up in this conversation instead: confirm the repositories to watch, the trigger label, the branch prefix, whether pull requests open as drafts, and the polling schedule, then create the automation."
+  }
+}

package/automations/catalog/github-pr-reviewer/manifest.json

@@ -1,5 +1,6 @@
 {
   "id": "github-pr-reviewer",
+  "version": "1.0.0",
   "name": "GitHub Code Review Agent",
   "category": "Code review",
   "description": "Watch for a configurable label on GitHub pull requests, inspect full PR and repository context, and post an AI review comment once per label event.",
@@ -16,6 +17,11 @@
   "popularityRank": 100,
   "estimatedSetupMinutes": 4,
   "exampleImplementation": "Trigger: cron polling for open GitHub PRs with a configured label such as openhands-review\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN, with permission to write pull request reviews\n\n1. Read the repositories, trigger label, review tone, and polling schedule from setup.\n2. Poll each repository independently, with its own state, so PR numbers never collide.\n3. List open PRs and find the latest matching GitHub labeled issue event for each labeled PR.\n4. Deduplicate on the label event ID so every label application queues exactly one review.\n5. Extract the PR head commit into a directory of its own and start an OpenHands conversation with that directory as its workspace, so the agent reviews the exact commit without cloning anything.\n6. Post an acknowledgement with the conversation link, then confirm on GitHub that the review was published for that head SHA, falling back to posting the agent's text as a comment.\n7. Remove the checkout once the conversation has stopped, so nothing accumulates between runs.",
+  "impact": {
+    "basis": "completed-runs",
+    "one": "1 PR review sweep completed",
+    "other": "{{count}} PR review sweeps completed"
+  },
   "setup": {
     "version": "1.0",
     "mode": "direct",

package/automations/catalog/github-repo-monitor/manifest.json

@@ -1,5 +1,6 @@
 {
   "id": "github-repo-monitor",
+  "version": "1.0.0",
   "name": "GitHub repository monitor",
   "category": "Developer tools",
   "description": "Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.",
@@ -17,6 +18,11 @@
   "popularityRank": 98,
   "estimatedSetupMinutes": 5,
   "exampleImplementation": "Trigger: cron polling (e.g. every 15 minutes, configurable)\nRequired secret: GITHUB_PERSONAL_ACCESS_TOKEN\n\n1. Poll GitHub for new issue and PR comments since the last run.\n2. Match comments containing the trigger phrase (case-insensitive, default: @OpenHands).\n3. Post an acknowledgment comment with a link to the new OpenHands conversation.\n4. Forward follow-up replies in the same thread to the running conversation.\n5. Post the agent's final response back to GitHub when the conversation completes.",
+  "impact": {
+    "basis": "completed-runs",
+    "one": "1 repo scan completed",
+    "other": "{{count}} repo scans completed"
+  },
   "setup": {
     "version": "1.0",
     "mode": "direct",

package/automations/catalog/jira-issue-to-bitbucket-pr/manifest.json

@@ -0,0 +1,23 @@
+{
+  "id": "jira-issue-to-bitbucket-pr",
+  "name": "Jira issue to Bitbucket PR",
+  "category": "Project management",
+  "description": "Watch Jira for implementation-ready issues, start an agent to make the requested code change, and open a Bitbucket pull request.",
+  "requires": {
+    "integrations": {
+      "jira": {
+        "message": "Reads implementation-ready issues and posts progress back to Jira."
+      },
+      "bitbucket": {
+        "message": "Clones the target repository, pushes a branch, and opens the pull request."
+      }
+    },
+    "features": [
+      "conversationDispatch"
+    ]
+  },
+  "popularityRank": 83,
+  "estimatedSetupMinutes": 6,
+  "skill": "ticket-to-code-change",
+  "exampleImplementation": "Trigger: Jira issue marked implementation-ready\nRequired integrations: Jira, Bitbucket\n\n1. Watch the selected Jira team or project for issues carrying a configurable implementation-ready label or state.\n2. Deduplicate issue IDs so each transition dispatches once.\n3. Read the issue, linked dependencies, acceptance criteria, and target repository.\n4. Start an independent OpenHands conversation that clones the Bitbucket repository, creates an issue-keyed branch, implements and tests the change, and opens a pull request.\n5. Post the conversation and pull request links back to the Jira issue and update its status according to the team's workflow."
+}

package/automations/catalog/jira-issue-to-gitlab-mr/manifest.json

@@ -0,0 +1,23 @@
+{
+  "id": "jira-issue-to-gitlab-mr",
+  "name": "Jira issue to GitLab MR",
+  "category": "Project management",
+  "description": "Watch Jira for implementation-ready issues, start an agent to make the requested code change, and open a GitLab merge request.",
+  "requires": {
+    "integrations": {
+      "jira": {
+        "message": "Reads implementation-ready issues and posts progress back to Jira."
+      },
+      "gitlab": {
+        "message": "Clones the target repository, pushes a branch, and opens the merge request."
+      }
+    },
+    "features": [
+      "conversationDispatch"
+    ]
+  },
+  "popularityRank": 84,
+  "estimatedSetupMinutes": 6,
+  "skill": "ticket-to-code-change",
+  "exampleImplementation": "Trigger: Jira issue marked implementation-ready\nRequired integrations: Jira, GitLab\n\n1. Watch the selected Jira team or project for issues carrying a configurable implementation-ready label or state.\n2. Deduplicate issue IDs so each transition dispatches once.\n3. Read the issue, linked dependencies, acceptance criteria, and target repository.\n4. Start an independent OpenHands conversation that clones the GitLab repository, creates an issue-keyed branch, implements and tests the change, and opens a merge request.\n5. Post the conversation and merge request links back to the Jira issue and update its status according to the team's workflow."
+}

package/automations/catalog/linear-issue-to-bitbucket-pr/manifest.json

@@ -0,0 +1,23 @@
+{
+  "id": "linear-issue-to-bitbucket-pr",
+  "name": "Linear issue to Bitbucket PR",
+  "category": "Project management",
+  "description": "Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a Bitbucket pull request.",
+  "requires": {
+    "integrations": {
+      "linear": {
+        "message": "Reads implementation-ready issues and posts progress back to Linear."
+      },
+      "bitbucket": {
+        "message": "Clones the target repository, pushes a branch, and opens the pull request."
+      }
+    },
+    "features": [
+      "conversationDispatch"
+    ]
+  },
+  "popularityRank": 87,
+  "estimatedSetupMinutes": 6,
+  "skill": "ticket-to-code-change",
+  "exampleImplementation": "Trigger: Linear issue marked implementation-ready\nRequired integrations: Linear, Bitbucket\n\n1. Watch the selected Linear team or project for issues carrying a configurable implementation-ready label or state.\n2. Deduplicate issue IDs so each transition dispatches once.\n3. Read the issue, linked dependencies, acceptance criteria, and target repository.\n4. Start an independent OpenHands conversation that clones the Bitbucket repository, creates an issue-keyed branch, implements and tests the change, and opens a pull request.\n5. Post the conversation and pull request links back to the Linear issue and update its status according to the team's workflow."
+}

package/automations/catalog/linear-issue-to-github-pr/manifest.json

@@ -0,0 +1,23 @@
+{
+  "id": "linear-issue-to-github-pr",
+  "name": "Linear issue to GitHub PR",
+  "category": "Project management",
+  "description": "Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a GitHub pull request.",
+  "requires": {
+    "integrations": {
+      "linear": {
+        "message": "Reads implementation-ready issues and posts progress back to Linear."
+      },
+      "github": {
+        "message": "Clones the target repository, pushes a branch, and opens the pull request."
+      }
+    },
+    "features": [
+      "conversationDispatch"
+    ]
+  },
+  "popularityRank": 89,
+  "estimatedSetupMinutes": 6,
+  "skill": "ticket-to-code-change",
+  "exampleImplementation": "Trigger: Linear issue marked implementation-ready\nRequired integrations: Linear, GitHub\n\n1. Watch the selected Linear team or project for issues carrying a configurable implementation-ready label or state.\n2. Deduplicate issue IDs so each transition dispatches once.\n3. Read the issue, linked dependencies, acceptance criteria, and target repository.\n4. Start an independent OpenHands conversation that clones the GitHub repository, creates an issue-keyed branch, implements and tests the change, and opens a pull request.\n5. Post the conversation and pull request links back to the Linear issue and update its status according to the team's workflow."
+}

package/automations/catalog/linear-issue-to-gitlab-mr/manifest.json

@@ -0,0 +1,23 @@
+{
+  "id": "linear-issue-to-gitlab-mr",
+  "name": "Linear issue to GitLab MR",
+  "category": "Project management",
+  "description": "Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a GitLab merge request.",
+  "requires": {
+    "integrations": {
+      "linear": {
+        "message": "Reads implementation-ready issues and posts progress back to Linear."
+      },
+      "gitlab": {
+        "message": "Clones the target repository, pushes a branch, and opens the merge request."
+      }
+    },
+    "features": [
+      "conversationDispatch"
+    ]
+  },
+  "popularityRank": 88,
+  "estimatedSetupMinutes": 6,
+  "skill": "ticket-to-code-change",
+  "exampleImplementation": "Trigger: Linear issue marked implementation-ready\nRequired integrations: Linear, GitLab\n\n1. Watch the selected Linear team or project for issues carrying a configurable implementation-ready label or state.\n2. Deduplicate issue IDs so each transition dispatches once.\n3. Read the issue, linked dependencies, acceptance criteria, and target repository.\n4. Start an independent OpenHands conversation that clones the GitLab repository, creates an issue-keyed branch, implements and tests the change, and opens a merge request.\n5. Post the conversation and merge request links back to the Linear issue and update its status according to the team's workflow."
+}

package/automations/catalog/news-digest/manifest.json

@@ -0,0 +1,81 @@
+{
+  "id": "news-digest",
+  "name": "Daily news digest",
+  "category": "Research",
+  "icon": "activity",
+  "description": "Read a list of public RSS and Atom feeds on a schedule, hand an agent everything new, and have it pick out what matters for your topics and write a short digest. Connects to nothing and needs no credentials.",
+  "requires": {
+    "integrations": {},
+    "features": [
+      "customTarball"
+    ]
+  },
+  "popularityRank": 78,
+  "estimatedSetupMinutes": 2,
+  "exampleImplementation": "Trigger: cron, daily by default (0 8 * * *)\nRequired secret: none. The feeds are public URLs and the conversation is started with an empty secret allow-list and no MCP servers.\n\n1. Read the feed list, the topics, and the schedule from setup.\n2. Key one unit of work to the UTC date, so a cron that fires more often, a retried run, or a restarted service cannot write the same digest twice.\n3. Fetch every feed over plain HTTPS and parse RSS 2.0, RSS 1.0/RDF and Atom by local element name. A feed that is down, moved, or no longer a feed is reported and skipped; the run fails only when every feed fails.\n4. Drop stories already covered by an earlier digest and stories older than the lookback window. Do not judge what a story is about: that has no right answer and is the agent's call.\n5. Start no conversation at all when nothing new was published, and leave the day open for a later run. A quiet day costs no tokens.\n6. Otherwise start an OpenHands conversation with the newest stories and the topics in the prompt, and let it decide which are relevant, group them, merge duplicate coverage, and write the digest.\n7. Deliver it three ways that need no credentials: it stays in the conversation, it is printed into the run log, and its opening is kept in state.\n8. Remember the reported stories only once a digest exists, so a failed run is recovered by the next one rather than lost.",
+  "impact": {
+    "basis": "completed-runs",
+    "one": "1 feed check completed",
+    "other": "{{count}} feed checks completed"
+  },
+  "setup": {
+    "version": "1.0",
+    "mode": "direct",
+    "form": {
+      "triggers": {
+        "cron": {
+          "schedule": {
+            "type": "cron",
+            "label": "Digest time",
+            "help": "When the digest is written. Work is keyed by UTC date, so a schedule more frequent than daily only polls until there is something new.",
+            "default": "0 8 * * *",
+            "required": true
+          },
+          "timezone": {
+            "type": "timezone",
+            "label": "Timezone",
+            "help": "Timezone the schedule is interpreted in.",
+            "default": "UTC",
+            "required": true
+          }
+        }
+      },
+      "args": {
+        "feeds": {
+          "type": "textarea",
+          "label": "Feeds",
+          "help": "One RSS or Atom feed URL per line. They must be public: this automation signs in to nothing, so a feed behind a login will simply fail and be skipped.",
+          "default": "https://news.ycombinator.com/rss\nhttps://feeds.arstechnica.com/arstechnica/index\nhttps://www.theverge.com/rss/index.xml",
+          "required": true,
+          "constraints": {
+            "minLength": 8,
+            "maxLength": 4000
+          }
+        },
+        "topics": {
+          "type": "textarea",
+          "label": "Topics of interest",
+          "help": "One topic per line, or separated by commas. The agent reads every new story and decides which ones are about these, so write them the way you would explain your interests to a colleague rather than as search terms. Leave this empty to cover whatever is most significant.",
+          "default": "artificial intelligence, open source, developer tools",
+          "required": false,
+          "constraints": {
+            "maxLength": 2000
+          }
+        }
+      }
+    },
+    "bundle": {
+      "version": "1.0.0",
+      "entrypoint": "python3 main.py",
+      "timeout": 900,
+      "files": {
+        "main.py": "skills/news-digest/scripts/main.py"
+      },
+      "config": {
+        "feeds": "{{form.feeds}}",
+        "topics": "{{form.topics}}"
+      }
+    },
+    "message": "This deployment cannot run the scheduled news digest directly. Set it up in this conversation instead: confirm the feeds to read, the topics to watch for, and the schedule, then create the automation."
+  }
+}

package/automations/catalog/qa-changes/manifest.json

@@ -0,0 +1,72 @@
+{
+  "id": "qa-changes",
+  "name": "QA Changes Agent",
+  "category": "Code review",
+  "description": "When a pull request is opened for review, run the QA changes methodology — set up the environment, exercise the changed behavior as a real user would, and post the outcome by editing the PR description with a QA Agent section.",
+  "requires": {
+    "integrations": {
+      "github": {
+        "message": "Used to read the pull request, check the author's commit history, and edit the PR description."
+      }
+    },
+    "features": [
+      "repoClone",
+      "presetPrompt",
+      "webhookDelivery"
+    ]
+  },
+  "popularityRank": 85,
+  "estimatedSetupMinutes": 5,
+  "skill": "qa-changes",
+  "exampleImplementation": "Trigger: GitHub pull_request.opened and pull_request.ready_for_review events\nRequired secret: GITHUB_TOKEN\n\n1. Receive a GitHub pull_request event (opened or ready_for_review).\n2. Filter: the PR must not be a draft (draft == false), the PR description must not already contain a QA Agent section, and the PR author must have more than 3 commits already in main.\n3. Start an OpenHands conversation that clones the repo, checks out the PR head, and runs the /qa-changes methodology: understand the change, set up the environment, exercise the changed behavior as a real user would.\n4. Instead of posting a review comment, edit the PR description to append a horizontal rule followed by a QA Agent section containing the structured QA report.",
+  "setup": {
+    "version": "1.0",
+    "mode": "direct",
+    "form": {
+      "triggers": {
+        "event": {
+          "on": {
+            "type": "select",
+            "label": "Trigger on",
+            "help": "Which GitHub pull request event starts a QA run. Opened fires when a non-draft PR is created; Ready for review fires when a draft PR is marked ready.",
+            "default": "pull_request.opened",
+            "required": true,
+            "options": [
+              {
+                "value": "pull_request.opened",
+                "label": "Pull request opened"
+              },
+              {
+                "value": "pull_request.ready_for_review",
+                "label": "Pull request ready for review"
+              }
+            ]
+          }
+        }
+      },
+      "args": {
+        "repository": {
+          "type": "repo-picker",
+          "label": "Repository",
+          "help": "The repository whose pull requests will be QA'd.",
+          "provider": "github",
+          "required": true
+        },
+        "ref": {
+          "type": "text",
+          "label": "Base branch",
+          "help": "Branch checked out when the agent runs QA.",
+          "default": "main",
+          "required": true,
+          "constraints": {
+            "minLength": 1,
+            "maxLength": 255
+          }
+        }
+      }
+    },
+    "prompt": "A pull request was opened or marked ready for review in {{form.repository}}. Before doing any QA work, run these gate checks and stop immediately (making no changes) if any fails:\n\n1. The PR must not be a draft — it must be open for review. If the PR is a draft, stop.\n2. The PR author (the human who opened it) must have more than 3 commits already merged into the {{form.ref}} branch. Use the GitHub API to count the author's commits in {{form.ref}}. If the count is 3 or fewer, stop without making any changes.\n3. The PR description must not already contain a section named QA Agent (i.e., a header like ## QA Agent or ### QA Agent). If that section already exists, stop without making any changes or starting a conversation.\n\nIf all gate checks pass, proceed with the QA validation using the /qa-changes skill methodology:\n\n- Phase 1: Understand the change. Read the PR diff, title, and description. Identify the goal of the PR. Classify every changed file. Form a hypothesis about what the PR should achieve.\n- Phase 2: Set up the environment. Read the repo's bootstrap instructions, install dependencies, and build if needed. Note CI status but do not re-run tests.\n- Phase 3: Exercise the changed behavior. Actually run the software the way a real user would — start servers, run CLI commands, make HTTP requests, open browsers. Do NOT run the test suite, linters, or code analysis. For bug fixes, reproduce the bug before and after the fix. Show before/after evidence.\n- Phase 4: Report results.\n\nIMPORTANT — how to post your report:\nDo NOT post a new comment, review, or inline review comment. Instead, EDIT the PR description (the pull request body) to append your QA report at the very end, after a horizontal rule (---), under a new section titled QA Agent. Use the GitHub API (PATCH /repos/{owner}/{repo}/pulls/{pr_number} with a body field) to update the PR description. Append the following structure to the existing PR body:\n\n---\n\n## QA Agent\n\n{Your full QA report following the /qa-changes skill report format: verdict, summary, Does this PR achieve its stated goal? section, status table, collapsible evidence in details blocks, and issues found.}\n\nDo not make any other changes to the PR description — only append the QA Agent section at the end. Do not post any comments or reviews.",
+    "filter": "!pull_request.draft && !icontains(pull_request.body, 'QA Agent') && glob(repository.full_name, '{{form.repository}}')",
+    "message": "This deployment cannot run the webhook-driven QA automation directly. Set it up in this conversation instead: confirm the repository to QA, the base branch, and the PR event to trigger on, then create the automation."
+  }
+}

package/automations/catalog/slack-github-linear-daily-organization.json

@@ -0,0 +1,27 @@
+{
+  "id": "slack-github-linear-daily-organization",
+  "name": "Slack + GitHub + Linear daily organization",
+  "category": "Personal productivity",
+  "description": "Every morning, reconcile your open GitHub PRs with Linear issues, align active work, surface relevant Slack context, and send yourself a concise daily plan.",
+  "exampleImplementation": "Trigger: cron, every morning at 7:00 AM in the configured timezone\nRequired integrations: GitHub, Linear, Slack\n\n1. Verify access to all three services before making changes.\n2. Reconcile open GitHub PRs with issues and import missing issues into Linear.\n3. Align active Linear work with open PRs and recent Slack context.\n4. Send a concise, prioritized daily plan to the configured Slack recipient.",
+  "requiredIntegrationIds": [
+    "slack",
+    "github",
+    "linear"
+  ],
+  "popularityRank": 88,
+  "estimatedSetupMinutes": 10,
+  "suggestedTrigger": {
+    "type": "cron",
+    "schedule": "0 7 * * *",
+    "timezone": "[IANA_TIMEZONE]"
+  },
+  "placeholders": [
+    "[GITHUB_USERNAME]",
+    "[LINEAR_ASSIGNEE_QUERY]",
+    "[GITHUB_ORG_OR_REPO_SCOPE]",
+    "[SLACK_RECIPIENT_QUERY]",
+    "[IANA_TIMEZONE]"
+  ],
+  "prompt": "You are running a daily GitHub/Linear/Slack organization automation.\n\nSchedule context:\n- This automation runs every morning at 7:00 AM in [IANA_TIMEZONE].\n- Treat \"today\" and \"past 1-3 days\" in [IANA_TIMEZONE].\n\nImportant safety and access rules:\n1. First, verify that you have working access to GitHub, Linear, and Slack using the available official tools/APIs. A minimal successful read for each service is enough.\n2. If any one of GitHub, Linear, or Slack is unavailable, missing credentials, or returns an authorization error, stop immediately. Do not make partial updates. If Slack is available, send the configured Slack recipient a short message saying which service was unavailable and that no changes were made; otherwise finish with that error.\n3. Prefer official APIs/MCP tools over browser interaction. Do not browse web UIs unless no API/tool path exists.\n4. When posting to Slack or creating/updating human-readable external-service content, include a short disclosure that the content was generated by an AI agent (OpenHands) on behalf of the user.\n\nIdentity and scope:\n- GitHub user to inspect: [GITHUB_USERNAME].\n- GitHub issue scope: [GITHUB_ORG_OR_REPO_SCOPE]. Examples: visible repositories in one or more organizations, or an explicit allowlist of repositories.\n- Linear assignee: resolve by searching for [LINEAR_ASSIGNEE_QUERY]. Do not guess an ID if multiple plausible matches exist.\n- Slack recipient for the final daily plan: resolve by searching for [SLACK_RECIPIENT_QUERY], or use the current authenticated Slack user if that is the intended recipient.\n\nTask 1 — Ensure the user's open PRs are associated with GitHub issues:\n1. Find all open pull requests authored by [GITHUB_USERNAME] across the configured GitHub scope.\n2. For each PR, determine whether it is already associated with a GitHub issue. Count an association if the PR body has a clear issue reference or closing keyword (for example, #123, owner/repo#123, fixes, closes, or resolves), or if GitHub's API exposes linked/closing issues.\n3. If a PR has no associated issue:\n   a. Search open issues in the same repository for an obvious matching issue using the PR title, branch name, and summary. Only treat an issue as obvious if the title/topic clearly matches; do not force weak matches.\n   b. If an obvious open issue exists, use that issue.\n   c. If none exists, create a new GitHub issue in the same repository summarizing the PR's purpose and linking back to the PR. Include an AI disclosure in the issue body.\n   d. Update the PR description to include a non-closing association such as \"Related issue: #123\" or \"Related issue: owner/repo#123\" for cross-repo references. Preserve the existing PR description. Avoid \"Fixes\", \"Closes\", or \"Resolves\" unless the PR already used a closing keyword or the issue clearly should close when the PR merges.\n\nTask 2 — Ensure GitHub issues are represented in Linear:\n1. Find all open GitHub issues, excluding PRs, in the configured GitHub issue scope.\n2. For each issue, verify that it has a corresponding Linear issue. Match by GitHub issue URL first, then by exact repository/name/number and title if needed.\n3. If no Linear issue exists, create one in the appropriate Linear team/project using the GitHub issue title, URL, repository, labels, and a concise summary. Include an AI disclosure in the Linear issue description. Choose an appropriate priority for newly created Linear issues using this rubric:\n   - Urgent: security, production outage, data loss, severe user-blocking regression, active incident.\n   - High: important bug/regression, release blocker, broadly affecting users, high-value requested work.\n   - Medium: normal feature/bug/task with moderate impact.\n   - Low: cleanup, docs, nice-to-have, unclear/low-impact backlog.\n   - No priority only if there is insufficient information.\n4. For every GitHub issue that has one or more open PRs associated with it, ensure the corresponding Linear issue is assigned to the configured Linear assignee and has a started/In Progress status. If the Linear issue is already completed or canceled, do not reopen it; mention this in the final report instead.\n5. Do not downgrade or otherwise change priorities of existing Linear issues merely because they seem wrong. If an existing priority is missing and the issue is actively in progress due to an open PR, you may set a reasonable priority. If a priority seems unclear or incorrect, flag it in the final Slack report rather than changing it.\n\nTask 3 — Check Slack context for active Linear issues:\n1. Inspect active Linear issues assigned to the configured assignee and not completed/canceled, especially urgent, high-priority, and in-progress issues.\n2. Search Slack public content and, if available in the tool configuration, private/DM-accessible content for the last 1-3 days for requests, mentions, or discussions related to those Linear issue identifiers, issue titles, linked GitHub issues/PRs, and relevant repository names.\n3. Summarize actionable Slack requests/discussions. Include links to Slack messages/threads when the Slack tooling provides them.\n4. Do not expose private Slack content beyond what is necessary for the configured recipient's own daily plan.\n\nTask 4 — Produce and send the daily plan:\n1. Review all active Linear issues assigned to the configured assignee, prioritizing Urgent then High then Medium then Low, while also considering Slack requests, open PR status, blockers, and issue age.\n2. Create a concise plan for what the recipient should work on today, focusing on the most urgent and important issues first.\n3. Include:\n   - Top 3-5 recommended focus items with Linear identifiers/titles and links.\n   - Any GitHub PR issue-association work performed.\n   - Any GitHub issues imported into Linear.\n   - Any Linear issues moved to In Progress or assigned to the configured assignee because an open PR exists.\n   - Any Slack requests/discussions from the past 1-3 days relevant to active Linear issues.\n   - Any issue priorities that are unclear or appear incorrect; explicitly say you did not change those priorities.\n   - Any access or matching limitations.\n4. Send the report to the configured Slack recipient as a DM if possible. If DM is not possible, use the best available Slack destination for that recipient. Include the AI disclosure in the message.\n5. Finish with a short execution summary including counts of PRs checked, PRs updated, GitHub issues created, GitHub issues imported to Linear, Linear issues updated, and Slack discussions found.\n\nBe careful and conservative: avoid duplicate GitHub issues, duplicate Linear issues, weak associations, or broad destructive changes."
+}

package/automations/catalog-index.js

@@ -4,13 +4,22 @@
 
 import entry0 from "./catalog/github-pr-reviewer/manifest.json" with { type: "json" };
 import entry1 from "./catalog/github-repo-monitor/manifest.json" with { type: "json" };
-import entry2 from "./catalog/slack-standup-digest/manifest.json" with { type: "json" };
-import entry3 from "./catalog/slack-channel-monitor/manifest.json" with { type: "json" };
-import entry4 from "./catalog/linear-triage-assistant/manifest.json" with { type: "json" };
-import entry5 from "./catalog/jira-issue-to-pr/manifest.json" with { type: "json" };
-import entry6 from "./catalog/research-brief-writer/manifest.json" with { type: "json" };
-import entry7 from "./catalog/upstream-fork-sync/manifest.json" with { type: "json" };
-import entry8 from "./catalog/incident-retrospective-drafter/manifest.json" with { type: "json" };
+import entry2 from "./catalog/github-issue-to-pr/manifest.json" with { type: "json" };
+import entry3 from "./catalog/slack-standup-digest/manifest.json" with { type: "json" };
+import entry4 from "./catalog/slack-channel-monitor/manifest.json" with { type: "json" };
+import entry5 from "./catalog/linear-triage-assistant/manifest.json" with { type: "json" };
+import entry6 from "./catalog/linear-issue-to-github-pr/manifest.json" with { type: "json" };
+import entry7 from "./catalog/linear-issue-to-gitlab-mr/manifest.json" with { type: "json" };
+import entry8 from "./catalog/linear-issue-to-bitbucket-pr/manifest.json" with { type: "json" };
+import entry9 from "./catalog/jira-issue-to-pr/manifest.json" with { type: "json" };
+import entry10 from "./catalog/qa-changes/manifest.json" with { type: "json" };
+import entry11 from "./catalog/jira-issue-to-gitlab-mr/manifest.json" with { type: "json" };
+import entry12 from "./catalog/research-brief-writer/manifest.json" with { type: "json" };
+import entry13 from "./catalog/jira-issue-to-bitbucket-pr/manifest.json" with { type: "json" };
+import entry14 from "./catalog/github-agents-md-maintainer/manifest.json" with { type: "json" };
+import entry15 from "./catalog/upstream-fork-sync/manifest.json" with { type: "json" };
+import entry16 from "./catalog/incident-retrospective-drafter/manifest.json" with { type: "json" };
+import entry17 from "./catalog/news-digest/manifest.json" with { type: "json" };
 
 export const AUTOMATION_CATALOG_ENTRIES = [
   entry0,
@@ -22,4 +31,13 @@ export const AUTOMATION_CATALOG_ENTRIES = [
   entry6,
   entry7,
   entry8,
+  entry9,
+  entry10,
+  entry11,
+  entry12,
+  entry13,
+  entry14,
+  entry15,
+  entry16,
+  entry17,
 ];