npm - @openhands/agent-canvas - Versions diffs - 1.14.0 → 1.16.0 - Mend

@openhands/agent-canvas 1.14.0 → 1.16.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (1855) hide show

package/dist/node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.js.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.json"],"sourcesContent":["{\n \"id\": \"github-repo-monitor\",\n \"name\": \"GitHub repository monitor\",\n \"category\": \"Developer tools\",\n \"description\": \"Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.\",\n \"requires\": {\n \"integrations\": {\n \"github\": {\n \"message\": \"Used to read issue and pull request comments and post replies.\"\n }\n },\n \"features\": [\n \"repoClone\",\n \"presetPrompt\"~~,\n~~ \~~"webhookDelivery\"\~~n ]\n },\n \"popularityRank\": 98,\n \"estimatedSetupMinutes\": 5,\n \"exampleImplementation\": \"Trigger: cron, every ~~minute~~ (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.\",\n \"setup\": {\n \"version\": \"1.0\",\n \"mode\": \"direct\",\n \"form\": {\n \"triggers\": {\n \"~~event~~\": {\n \"on\": {\n \"type\": \"~~select~~\",\n \"label\": \"~~Respond~~ to\",\n \"help\": \"~~Which~~ ~~GitHub~~ ~~comment~~ ~~event~~ ~~starts~~ a ~~conversation~~.\",\n \"default\": \"~~issue_comment.created\~~",\n \"required\": true,\n \"~~options~~\": ~~[\n~~ {\n \"~~value~~\": \"~~issue_comment.created~~\",\n \"label\": \"~~Comments~~ on ~~issues~~ ~~and~~ ~~pull~~ ~~requests\~~"~~\n }~~,\n {\~~n \~~"~~value~~\": \"~~pull_request_review_comment.created~~\",\n \"~~label~~\": \~~"Pull request review comments only\"\~~n }\n ]\n },\n \"~~triggerPhrase~~\": {\n \"type\": \"~~text~~\",\n \"label\": \"~~Trigger phrase~~\",\n \"help\": \"~~Only~~ ~~comments~~ ~~containing~~ ~~this~~ ~~phrase~~ ~~start~~ a ~~conversation. Matched case-insensitively. Quotes and backslashes are not allowed, because the phrase becomes part of the event filter expression~~.\",\n \"~~default~~\": \"~~@openhands~~\",\n \"required\": true,\n \"~~constraints~~\": {\n \"~~minLength~~\": ~~2,\n~~ \"~~maxLength~~\"~~: 50~~,\n \"~~format~~\": \"~~safeExpressionLiteral~~\"\n ~~}\n~~ }\~~n }\n },\n \~~"~~args~~\": {\~~n \~~"~~repository\~~"~~: {\~~n \"~~type~~\": \"~~repo-picker~~\",\n \"~~label~~\": ~~\"Repository\"~~,\n \"~~help~~\": \~~"The repository or repositories to watch for mentions.\",\~~n \"~~provider~~\": ~~\"github\"~~,\n \"~~required~~\": ~~true~~\n },\n \"ref\": {\n \"type\": \"text\",\n \"label\": \"Base branch\",\n \"help\": \"Branch checked out when the agent responds.\",\n \"default\": \"main\",\n \"required\": true,\n \"constraints\": {\n \"minLength\": 1,\n \"maxLength\": 255\n }\n }\n }\n },\n \"prompt\": \"A ~~comment in~~ {{form.repository}} ~~mentions~~ '{{form.triggerPhrase}}'. ~~Read~~ the surrounding issue or pull request context ~~from~~ ~~the event payload, then~~ post a helpful reply as a comment on the same thread.\",\n \"~~filter\": \"icontains(comment.body, '{{form.triggerPhrase}}') && glob(repository.full_name, '{{form.repository}}')\",\n \"~~message\": \"This deployment cannot run the ~~webhook-driven~~ monitor directly. Set it up in this conversation instead: confirm the repository to watch, the ~~comment~~ ~~event~~, and the ~~trigger~~ ~~phrase~~, then create the automation~~. If webhook delivery is unavailable here, build the polling variant this skill supports~~.\"\n }\n}\n"],"x_google_ignoreList":[0],"mappings":""}
1	+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/github-repo-monitor/manifest.json"],"sourcesContent":["{\n \"id\": \"github-repo-monitor\",\n \"version\": \"1.0.0\",\n \"name\": \"GitHub repository monitor\",\n \"category\": \"Developer tools\",\n \"description\": \"Watch a repository for @OpenHands mentions in issues and PR comments, start a conversation, and post the agent's reply back to GitHub.\",\n \"requires\": {\n \"integrations\": {\n \"github\": {\n \"message\": \"Used to read issue and pull request comments and post replies.\"\n }\n },\n \"features\": [\n \"repoClone\",\n \"presetPrompt\"\n ]\n },\n \"popularityRank\": 98,\n \"estimatedSetupMinutes\": 5,\n \"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.\",\n \"impact\": {\n \"basis\": \"completed-runs\",\n \"one\": \"1 repo scan completed\",\n \"other\": \"{{count}} repo scans completed\"\n },\n \"setup\": {\n \"version\": \"1.0\",\n \"mode\": \"direct\",\n \"form\": {\n \"triggers\": {\n \"cron\": {\n \"schedule\": {\n \"type\": \"cron\",\n \"label\": \"Check frequency\",\n \"help\": \"How often to look for new comments to respond to.\",\n \"default\": \"/15 * * *\",\n \"required\": true\n },\n \"timezone\": {\n \"type\": \"timezone\",\n \"label\": \"Timezone\",\n \"help\": \"Timezone the schedule is interpreted in.\",\n \"default\": \"UTC\",\n \"required\": true\n }\n }\n },\n \"args\": {\n \"repository\": {\n \"type\": \"repo-picker\",\n \"label\": \"Repository\",\n \"help\": \"The repository or repositories to watch for mentions.\",\n \"provider\": \"github\",\n \"required\": true\n },\n \"triggerPhrase\": {\n \"type\": \"text\",\n \"label\": \"Trigger phrase\",\n \"help\": \"Only comments containing this phrase start a conversation. Matched case-insensitively.\",\n \"default\": \"@openhands\",\n \"required\": true,\n \"constraints\": {\n \"minLength\": 2,\n \"maxLength\": 50\n }\n },\n \"ref\": {\n \"type\": \"text\",\n \"label\": \"Base branch\",\n \"help\": \"Branch checked out when the agent responds.\",\n \"default\": \"main\",\n \"required\": true,\n \"constraints\": {\n \"minLength\": 1,\n \"maxLength\": 255\n }\n }\n }\n },\n \"prompt\": \"Poll {{form.repository}} for any new issue or pull request comments since the last run. For every comment mentioning '{{form.triggerPhrase}}', read the surrounding issue or pull request context and post a helpful reply as a comment on the same thread.\",\n \"message\": \"This deployment cannot run the scheduled monitor directly. Set it up in this conversation instead: confirm the repository to watch, the trigger phrase, and the polling schedule, then create the automation.\"\n }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-bitbucket-pr/manifest.cjs ADDED Viewed

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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
+Required integrations: Jira, Bitbucket
+1. Watch the selected Jira team or project for issues carrying a configurable implementation-ready label or state.
+2. Deduplicate issue IDs so each transition dispatches once.
+3. Read the issue, linked dependencies, acceptance criteria, and target repository.
+4. 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.
+5. Post the conversation and pull request links back to the Jira issue and update its status according to the team's workflow.`};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-bitbucket-pr/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-bitbucket-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-bitbucket-pr\",\n \"name\": \"Jira issue to Bitbucket PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Jira for implementation-ready issues, start an agent to make the requested code change, and open a Bitbucket pull request.\",\n \"requires\": {\n \"integrations\": {\n \"jira\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Jira.\"\n },\n \"bitbucket\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the pull request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 83,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-bitbucket-pr/manifest.js ADDED Viewed

@@ -0,0 +1,21 @@
+var e = {
+	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."
+};
+//#endregion
+export { e as default };
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-bitbucket-pr/manifest.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-bitbucket-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-bitbucket-pr\",\n \"name\": \"Jira issue to Bitbucket PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Jira for implementation-ready issues, start an agent to make the requested code change, and open a Bitbucket pull request.\",\n \"requires\": {\n \"integrations\": {\n \"jira\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Jira.\"\n },\n \"bitbucket\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the pull request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 83,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-gitlab-mr/manifest.cjs ADDED Viewed

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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
+Required integrations: Jira, GitLab
+1. Watch the selected Jira team or project for issues carrying a configurable implementation-ready label or state.
+2. Deduplicate issue IDs so each transition dispatches once.
+3. Read the issue, linked dependencies, acceptance criteria, and target repository.
+4. 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.
+5. Post the conversation and merge request links back to the Jira issue and update its status according to the team's workflow.`};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-gitlab-mr/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-gitlab-mr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-gitlab-mr\",\n \"name\": \"Jira issue to GitLab MR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Jira for implementation-ready issues, start an agent to make the requested code change, and open a GitLab merge request.\",\n \"requires\": {\n \"integrations\": {\n \"jira\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Jira.\"\n },\n \"gitlab\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the merge request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 84,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-gitlab-mr/manifest.js ADDED Viewed

@@ -0,0 +1,21 @@
+var e = {
+	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."
+};
+//#endregion
+export { e as default };
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-gitlab-mr/manifest.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-gitlab-mr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-gitlab-mr\",\n \"name\": \"Jira issue to GitLab MR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Jira for implementation-ready issues, start an agent to make the requested code change, and open a GitLab merge request.\",\n \"requires\": {\n \"integrations\": {\n \"jira\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Jira.\"\n },\n \"gitlab\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the merge request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 84,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.cjs CHANGED Viewed

@@ -1,7 +1,7 @@
-require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={id:`jira-issue-to-pr`,name:`Jira issue to GitHub PR`,category:`Project management`,description:`Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.`,requires:{integrations:{jira:{message:`Reads the project for issues carrying the trigger label.`},github:{message:`Opens a pull request on the repository named in the ticket.`}}},popularityRank:85,estimatedSetupMinutes:5,exampleImplementation:`Trigger: cron polling (e.g. every 5 minutes)
-Required secrets: Jira API token, GitHub personal access token (repo + workflow scope)
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={id:`jira-issue-to-pr`,name:`Jira issue to GitHub PR`,category:`Project management`,description:`Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.`,requires:{integrations:{"atlassian-rovo":{message:`Provides the Atlassian Rovo MCP connection used to access Jira data.`},github:{message:`Opens a pull request on the repository named in the ticket.`}}},popularityRank:85,estimatedSetupMinutes:5,exampleImplementation:`Trigger: cron polling (e.g. every 5 minutes)
+Required integrations: Atlassian Rovo MCP for Jira access and a GitHub MCP connection. The poller also needs a Jira API token and a GitHub personal access token (repo + workflow scope) as secrets for its direct API calls.
-1. Collect Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.
+1. Connect Atlassian Rovo MCP and GitHub, then collect the Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.
 2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.
 3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.
 4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.cjs.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-pr\",\n \"name\": \"Jira issue to GitHub PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.\",\n \"requires\": {\n \"integrations\": {\n \"~~jira~~\": {\n \"message\": \"~~Reads~~ the ~~project~~ ~~for~~ ~~issues~~ ~~carrying~~ ~~the~~ ~~trigger~~ ~~label~~.\"\n },\n \"github\": {\n \"message\": \"Opens a pull request on the repository named in the ticket.\"\n }\n }\n },\n \"popularityRank\": 85,\n \"estimatedSetupMinutes\": 5,\n \"exampleImplementation\": \"Trigger: cron polling (e.g. every 5 minutes)\\nRequired ~~secrets~~: Jira API token, GitHub personal access token (repo + workflow scope)\\n\\n1. ~~Collect~~ Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.\\n2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.\\n3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.\\n4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.\\n5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.\\n6. Persist the processed issue key immediately after dispatching so the next poll skips it.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}
1	+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-pr\",\n \"name\": \"Jira issue to GitHub PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.\",\n \"requires\": {\n \"integrations\": {\n \"atlassian-rovo\": {\n \"message\": \"Provides the Atlassian Rovo MCP connection used to access Jira data.\"\n },\n \"github\": {\n \"message\": \"Opens a pull request on the repository named in the ticket.\"\n }\n }\n },\n \"popularityRank\": 85,\n \"estimatedSetupMinutes\": 5,\n \"exampleImplementation\": \"Trigger: cron polling (e.g. every 5 minutes)\\nRequired integrations: Atlassian Rovo MCP for Jira access and a GitHub MCP connection. The poller also needs a Jira API token and a GitHub personal access token (repo + workflow scope) as secrets for its direct API calls.\\n\\n1. Connect Atlassian Rovo MCP and GitHub, then collect the Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.\\n2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.\\n3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.\\n4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.\\n5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.\\n6. Persist the processed issue key immediately after dispatching so the next poll skips it.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.js CHANGED Viewed

@@ -4,12 +4,12 @@ var e = {
 	category: "Project management",
 	description: "Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.",
 	requires: { integrations: {
-		jira: { message: "Reads the project for issues carrying the trigger label." },
+		"atlassian-rovo": { message: "Provides the Atlassian Rovo MCP connection used to access Jira data." },
 		github: { message: "Opens a pull request on the repository named in the ticket." }
 	} },
 	popularityRank: 85,
 	estimatedSetupMinutes: 5,
-	exampleImplementation: "Trigger: cron polling (e.g. every 5 minutes)\nRequired secrets: Jira API token, GitHub personal access token (repo + workflow scope)\n\n1. Collect Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.\n2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.\n3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.\n4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.\n5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.\n6. Persist the processed issue key immediately after dispatching so the next poll skips it."
+	exampleImplementation: "Trigger: cron polling (e.g. every 5 minutes)\nRequired integrations: Atlassian Rovo MCP for Jira access and a GitHub MCP connection. The poller also needs a Jira API token and a GitHub personal access token (repo + workflow scope) as secrets for its direct API calls.\n\n1. Connect Atlassian Rovo MCP and GitHub, then collect the Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.\n2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.\n3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.\n4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.\n5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.\n6. Persist the processed issue key immediately after dispatching so the next poll skips it."
 };
 //#endregion
 export { e as default };

package/dist/node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.js.map CHANGED Viewed

	@@ -1 +1 @@
1	- {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-pr\",\n \"name\": \"Jira issue to GitHub PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.\",\n \"requires\": {\n \"integrations\": {\n \"~~jira~~\": {\n \"message\": \"~~Reads~~ the ~~project~~ ~~for~~ ~~issues~~ ~~carrying~~ ~~the~~ ~~trigger~~ ~~label~~.\"\n },\n \"github\": {\n \"message\": \"Opens a pull request on the repository named in the ticket.\"\n }\n }\n },\n \"popularityRank\": 85,\n \"estimatedSetupMinutes\": 5,\n \"exampleImplementation\": \"Trigger: cron polling (e.g. every 5 minutes)\\nRequired ~~secrets~~: Jira API token, GitHub personal access token (repo + workflow scope)\\n\\n1. ~~Collect~~ Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.\\n2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.\\n3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.\\n4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.\\n5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.\\n6. Persist the processed issue key immediately after dispatching so the next poll skips it.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}
1	+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/jira-issue-to-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"jira-issue-to-pr\",\n \"name\": \"Jira issue to GitHub PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch a Jira Cloud project for issues with a configurable label and automatically open a GitHub pull request for each new issue found. The target GitHub repo is read from the ticket body - no repo parameter required at deploy time.\",\n \"requires\": {\n \"integrations\": {\n \"atlassian-rovo\": {\n \"message\": \"Provides the Atlassian Rovo MCP connection used to access Jira data.\"\n },\n \"github\": {\n \"message\": \"Opens a pull request on the repository named in the ticket.\"\n }\n }\n },\n \"popularityRank\": 85,\n \"estimatedSetupMinutes\": 5,\n \"exampleImplementation\": \"Trigger: cron polling (e.g. every 5 minutes)\\nRequired integrations: Atlassian Rovo MCP for Jira access and a GitHub MCP connection. The poller also needs a Jira API token and a GitHub personal access token (repo + workflow scope) as secrets for its direct API calls.\\n\\n1. Connect Atlassian Rovo MCP and GitHub, then collect the Jira base URL, email, API token secret name, label to watch, and cron schedule from the user. No GitHub repo is needed at deploy time - each ticket must include the target repo (owner/repo) in its body.\\n2. Poll POST /rest/api/3/search/jql on the Jira Cloud instance to find open issues carrying the configured label.\\n3. Deduplicate against a KV-store-backed set of already-processed issue keys so re-runs never create duplicate PRs.\\n4. For each new issue, start an independent OpenHands agent conversation that extracts the GitHub repo from the ticket body, clones it, creates a branch named after the Jira key, implements or scaffolds the requested change, and opens a pull request.\\n5. Immediately after the conversation is created, post a Jira comment on the issue: 'I'm on it: <conversation URL>'.\\n6. Persist the processed issue key immediately after dispatching so the next poll skips it.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-bitbucket-pr/manifest.cjs ADDED Viewed

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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
+Required integrations: Linear, Bitbucket
+1. Watch the selected Linear team or project for issues carrying a configurable implementation-ready label or state.
+2. Deduplicate issue IDs so each transition dispatches once.
+3. Read the issue, linked dependencies, acceptance criteria, and target repository.
+4. 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.
+5. Post the conversation and pull request links back to the Linear issue and update its status according to the team's workflow.`};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-bitbucket-pr/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/linear-issue-to-bitbucket-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"linear-issue-to-bitbucket-pr\",\n \"name\": \"Linear issue to Bitbucket PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a Bitbucket pull request.\",\n \"requires\": {\n \"integrations\": {\n \"linear\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Linear.\"\n },\n \"bitbucket\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the pull request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 87,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-bitbucket-pr/manifest.js ADDED Viewed

@@ -0,0 +1,21 @@
+var e = {
+	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."
+};
+//#endregion
+export { e as default };
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-bitbucket-pr/manifest.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/linear-issue-to-bitbucket-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"linear-issue-to-bitbucket-pr\",\n \"name\": \"Linear issue to Bitbucket PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a Bitbucket pull request.\",\n \"requires\": {\n \"integrations\": {\n \"linear\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Linear.\"\n },\n \"bitbucket\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the pull request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 87,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-github-pr/manifest.cjs ADDED Viewed

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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
+Required integrations: Linear, GitHub
+1. Watch the selected Linear team or project for issues carrying a configurable implementation-ready label or state.
+2. Deduplicate issue IDs so each transition dispatches once.
+3. Read the issue, linked dependencies, acceptance criteria, and target repository.
+4. 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.
+5. Post the conversation and pull request links back to the Linear issue and update its status according to the team's workflow.`};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-github-pr/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/linear-issue-to-github-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"linear-issue-to-github-pr\",\n \"name\": \"Linear issue to GitHub PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a GitHub pull request.\",\n \"requires\": {\n \"integrations\": {\n \"linear\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Linear.\"\n },\n \"github\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the pull request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 89,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-github-pr/manifest.js ADDED Viewed

@@ -0,0 +1,21 @@
+var e = {
+	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."
+};
+//#endregion
+export { e as default };
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-github-pr/manifest.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/linear-issue-to-github-pr/manifest.json"],"sourcesContent":["{\n \"id\": \"linear-issue-to-github-pr\",\n \"name\": \"Linear issue to GitHub PR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a GitHub pull request.\",\n \"requires\": {\n \"integrations\": {\n \"linear\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Linear.\"\n },\n \"github\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the pull request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 89,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-gitlab-mr/manifest.cjs ADDED Viewed

@@ -0,0 +1,9 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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
+Required integrations: Linear, GitLab
+1. Watch the selected Linear team or project for issues carrying a configurable implementation-ready label or state.
+2. Deduplicate issue IDs so each transition dispatches once.
+3. Read the issue, linked dependencies, acceptance criteria, and target repository.
+4. 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.
+5. Post the conversation and merge request links back to the Linear issue and update its status according to the team's workflow.`};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-gitlab-mr/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/linear-issue-to-gitlab-mr/manifest.json"],"sourcesContent":["{\n \"id\": \"linear-issue-to-gitlab-mr\",\n \"name\": \"Linear issue to GitLab MR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a GitLab merge request.\",\n \"requires\": {\n \"integrations\": {\n \"linear\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Linear.\"\n },\n \"gitlab\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the merge request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 88,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-gitlab-mr/manifest.js ADDED Viewed

@@ -0,0 +1,21 @@
+var e = {
+	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."
+};
+//#endregion
+export { e as default };
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/linear-issue-to-gitlab-mr/manifest.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/linear-issue-to-gitlab-mr/manifest.json"],"sourcesContent":["{\n \"id\": \"linear-issue-to-gitlab-mr\",\n \"name\": \"Linear issue to GitLab MR\",\n \"category\": \"Project management\",\n \"description\": \"Watch Linear for implementation-ready issues, start an agent to make the requested code change, and open a GitLab merge request.\",\n \"requires\": {\n \"integrations\": {\n \"linear\": {\n \"message\": \"Reads implementation-ready issues and posts progress back to Linear.\"\n },\n \"gitlab\": {\n \"message\": \"Clones the target repository, pushes a branch, and opens the merge request.\"\n }\n },\n \"features\": [\n \"conversationDispatch\"\n ]\n },\n \"popularityRank\": 88,\n \"estimatedSetupMinutes\": 6,\n \"skill\": \"ticket-to-code-change\",\n \"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.\"\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/news-digest/manifest.cjs ADDED Viewed

@@ -0,0 +1,14 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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 * * *)
+Required secret: none. The feeds are public URLs and the conversation is started with an empty secret allow-list and no MCP servers.
+1. Read the feed list, the topics, and the schedule from setup.
+2. 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.
+3. 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.
+4. 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.
+5. 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.
+6. 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.
+7. 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.
+8. 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:!0},timezone:{type:`timezone`,label:`Timezone`,help:`Timezone the schedule is interpreted in.`,default:`UTC`,required:!0}}},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
+https://feeds.arstechnica.com/arstechnica/index
+https://www.theverge.com/rss/index.xml`,required:!0,constraints:{minLength:8,maxLength:4e3}},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:!1,constraints:{maxLength:2e3}}}},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.`}};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/news-digest/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/news-digest/manifest.json"],"sourcesContent":["{\n \"id\": \"news-digest\",\n \"name\": \"Daily news digest\",\n \"category\": \"Research\",\n \"icon\": \"activity\",\n \"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.\",\n \"requires\": {\n \"integrations\": {},\n \"features\": [\n \"customTarball\"\n ]\n },\n \"popularityRank\": 78,\n \"estimatedSetupMinutes\": 2,\n \"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.\",\n \"impact\": {\n \"basis\": \"completed-runs\",\n \"one\": \"1 feed check completed\",\n \"other\": \"{{count}} feed checks completed\"\n },\n \"setup\": {\n \"version\": \"1.0\",\n \"mode\": \"direct\",\n \"form\": {\n \"triggers\": {\n \"cron\": {\n \"schedule\": {\n \"type\": \"cron\",\n \"label\": \"Digest time\",\n \"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.\",\n \"default\": \"0 8 * * *\",\n \"required\": true\n },\n \"timezone\": {\n \"type\": \"timezone\",\n \"label\": \"Timezone\",\n \"help\": \"Timezone the schedule is interpreted in.\",\n \"default\": \"UTC\",\n \"required\": true\n }\n }\n },\n \"args\": {\n \"feeds\": {\n \"type\": \"textarea\",\n \"label\": \"Feeds\",\n \"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.\",\n \"default\": \"https://news.ycombinator.com/rss\\nhttps://feeds.arstechnica.com/arstechnica/index\\nhttps://www.theverge.com/rss/index.xml\",\n \"required\": true,\n \"constraints\": {\n \"minLength\": 8,\n \"maxLength\": 4000\n }\n },\n \"topics\": {\n \"type\": \"textarea\",\n \"label\": \"Topics of interest\",\n \"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.\",\n \"default\": \"artificial intelligence, open source, developer tools\",\n \"required\": false,\n \"constraints\": {\n \"maxLength\": 2000\n }\n }\n }\n },\n \"bundle\": {\n \"version\": \"1.0.0\",\n \"entrypoint\": \"python3 main.py\",\n \"timeout\": 900,\n \"files\": {\n \"main.py\": \"skills/news-digest/scripts/main.py\"\n },\n \"config\": {\n \"feeds\": \"{{form.feeds}}\",\n \"topics\": \"{{form.topics}}\"\n }\n },\n \"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.\"\n }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/news-digest/manifest.js ADDED Viewed

@@ -0,0 +1,77 @@
+var e = {
+	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: !0
+				},
+				timezone: {
+					type: "timezone",
+					label: "Timezone",
+					help: "Timezone the schedule is interpreted in.",
+					default: "UTC",
+					required: !0
+				}
+			} },
+			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: !0,
+					constraints: {
+						minLength: 8,
+						maxLength: 4e3
+					}
+				},
+				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: !1,
+					constraints: { maxLength: 2e3 }
+				}
+			}
+		},
+		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."
+	}
+};
+//#endregion
+export { e as default };
+//# sourceMappingURL=manifest.js.map

package/dist/node_modules/@openhands/extensions/automations/catalog/news-digest/manifest.js.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.js","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/news-digest/manifest.json"],"sourcesContent":["{\n \"id\": \"news-digest\",\n \"name\": \"Daily news digest\",\n \"category\": \"Research\",\n \"icon\": \"activity\",\n \"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.\",\n \"requires\": {\n \"integrations\": {},\n \"features\": [\n \"customTarball\"\n ]\n },\n \"popularityRank\": 78,\n \"estimatedSetupMinutes\": 2,\n \"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.\",\n \"impact\": {\n \"basis\": \"completed-runs\",\n \"one\": \"1 feed check completed\",\n \"other\": \"{{count}} feed checks completed\"\n },\n \"setup\": {\n \"version\": \"1.0\",\n \"mode\": \"direct\",\n \"form\": {\n \"triggers\": {\n \"cron\": {\n \"schedule\": {\n \"type\": \"cron\",\n \"label\": \"Digest time\",\n \"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.\",\n \"default\": \"0 8 * * *\",\n \"required\": true\n },\n \"timezone\": {\n \"type\": \"timezone\",\n \"label\": \"Timezone\",\n \"help\": \"Timezone the schedule is interpreted in.\",\n \"default\": \"UTC\",\n \"required\": true\n }\n }\n },\n \"args\": {\n \"feeds\": {\n \"type\": \"textarea\",\n \"label\": \"Feeds\",\n \"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.\",\n \"default\": \"https://news.ycombinator.com/rss\\nhttps://feeds.arstechnica.com/arstechnica/index\\nhttps://www.theverge.com/rss/index.xml\",\n \"required\": true,\n \"constraints\": {\n \"minLength\": 8,\n \"maxLength\": 4000\n }\n },\n \"topics\": {\n \"type\": \"textarea\",\n \"label\": \"Topics of interest\",\n \"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.\",\n \"default\": \"artificial intelligence, open source, developer tools\",\n \"required\": false,\n \"constraints\": {\n \"maxLength\": 2000\n }\n }\n }\n },\n \"bundle\": {\n \"version\": \"1.0.0\",\n \"entrypoint\": \"python3 main.py\",\n \"timeout\": 900,\n \"files\": {\n \"main.py\": \"skills/news-digest/scripts/main.py\"\n },\n \"config\": {\n \"feeds\": \"{{form.feeds}}\",\n \"topics\": \"{{form.topics}}\"\n }\n },\n \"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.\"\n }\n}\n"],"x_google_ignoreList":[0],"mappings":""}

package/dist/node_modules/@openhands/extensions/automations/catalog/qa-changes/manifest.cjs ADDED Viewed

@@ -0,0 +1,30 @@
+require("../../../../../../_virtual/_rolldown/runtime.cjs");var e={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
+Required secret: GITHUB_TOKEN
+1. Receive a GitHub pull_request event (opened or ready_for_review).
+2. 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.
+3. 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.
+4. 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:!0,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:!0},ref:{type:`text`,label:`Base branch`,help:`Branch checked out when the agent runs QA.`,default:`main`,required:!0,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:
+1. The PR must not be a draft — it must be open for review. If the PR is a draft, stop.
+2. 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.
+3. 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.
+If all gate checks pass, proceed with the QA validation using the /qa-changes skill methodology:
+- 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.
+- 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.
+- 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.
+- Phase 4: Report results.
+IMPORTANT — how to post your report:
+Do 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:
+---
+## QA Agent
+{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.}
+Do 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.`}};exports.default=e;
+//# sourceMappingURL=manifest.cjs.map

package/dist/node_modules/@openhands/extensions/automations/catalog/qa-changes/manifest.cjs.map ADDED Viewed

@@ -0,0 +1 @@

+ {"version":3,"file":"manifest.cjs","names":[],"sources":["../../../../../../../node_modules/@openhands/extensions/automations/catalog/qa-changes/manifest.json"],"sourcesContent":["{\n \"id\": \"qa-changes\",\n \"name\": \"QA Changes Agent\",\n \"category\": \"Code review\",\n \"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.\",\n \"requires\": {\n \"integrations\": {\n \"github\": {\n \"message\": \"Used to read the pull request, check the author's commit history, and edit the PR description.\"\n }\n },\n \"features\": [\n \"repoClone\",\n \"presetPrompt\",\n \"webhookDelivery\"\n ]\n },\n \"popularityRank\": 85,\n \"estimatedSetupMinutes\": 5,\n \"skill\": \"qa-changes\",\n \"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.\",\n \"setup\": {\n \"version\": \"1.0\",\n \"mode\": \"direct\",\n \"form\": {\n \"triggers\": {\n \"event\": {\n \"on\": {\n \"type\": \"select\",\n \"label\": \"Trigger on\",\n \"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.\",\n \"default\": \"pull_request.opened\",\n \"required\": true,\n \"options\": [\n {\n \"value\": \"pull_request.opened\",\n \"label\": \"Pull request opened\"\n },\n {\n \"value\": \"pull_request.ready_for_review\",\n \"label\": \"Pull request ready for review\"\n }\n ]\n }\n }\n },\n \"args\": {\n \"repository\": {\n \"type\": \"repo-picker\",\n \"label\": \"Repository\",\n \"help\": \"The repository whose pull requests will be QA'd.\",\n \"provider\": \"github\",\n \"required\": true\n },\n \"ref\": {\n \"type\": \"text\",\n \"label\": \"Base branch\",\n \"help\": \"Branch checked out when the agent runs QA.\",\n \"default\": \"main\",\n \"required\": true,\n \"constraints\": {\n \"minLength\": 1,\n \"maxLength\": 255\n }\n }\n }\n },\n \"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.\",\n \"filter\": \"!pull_request.draft && !icontains(pull_request.body, 'QA Agent') && glob(repository.full_name, '{{form.repository}}')\",\n \"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.\"\n }\n}\n"],"x_google_ignoreList":[0],"mappings":""}