{"metadata":{"name":"coding-bot","description":"Configuration pack for creating coding bots on GitHub using botdo.","version":"2.0","exportedAt":"2026-08-28T05:59:14.188170103Z"},"tools":[{"name":"apply_github_labels","description":"Apply one or more labels to a GitHub issue. Only use labels that exist in the repository — use list_github_labels first to check.","parameters":"[{\"name\":\"repo\",\"type\":\"string\",\"description\":\"Repository in owner/name format\",\"required\":true},{\"name\":\"issue_number\",\"type\":\"number\",\"description\":\"Issue number\",\"required\":true},{\"name\":\"labels\",\"type\":\"string\",\"description\":\"Comma-separated label names to apply\",\"required\":true}]","scriptTemplate":"botdo gh issue edit {{issue_number}} --repo {{repo}} --add-label \"{{labels}}\""},{"name":"create_github_pr","description":"Create a pull request on GitHub. The PR body is written to a temp file to avoid shell quoting issues.","parameters":"[{\"name\":\"repo\",\"type\":\"string\",\"description\":\"Repository in owner/name format\",\"required\":true},{\"name\":\"title\",\"type\":\"string\",\"description\":\"PR title\",\"required\":true},{\"name\":\"body\",\"type\":\"string\",\"description\":\"PR description (markdown)\",\"required\":true},{\"name\":\"head\",\"type\":\"string\",\"description\":\"Branch to merge from\",\"required\":true}]","scriptTemplate":"botdo gh pr create --repo {{repo}} --title \"{{title}}\" --body-file {{body_file}} --head {{head}}"},{"name":"list_github_issues","description":"List GitHub issues with filters for state, labels, and date range. Returns JSON with issue number, title, author, labels, and dates.","parameters":"[{\"name\":\"repo\",\"type\":\"string\",\"description\":\"Repository in owner/name format\",\"required\":true},{\"name\":\"state\",\"type\":\"string\",\"description\":\"Issue state: open, closed, or all\",\"required\":true},{\"name\":\"limit\",\"type\":\"number\",\"description\":\"Maximum number of issues to return\",\"required\":false}]","scriptTemplate":"botdo gh issue list --repo {{repo}} --state {{state}} --limit {{limit}} --json number,title,author,labels,createdAt,updatedAt,state"},{"name":"list_github_labels","description":"List all available labels in a GitHub repository with their names and descriptions, sorted by name. Use this to discover which labels exist before applying them to an issue.","parameters":"[{\"name\":\"repo\",\"type\":\"string\",\"description\":\"Repository in owner/name format\",\"required\":true}]","scriptTemplate":"botdo gh label list --repo {{repo}} --sort name --json name,description"},{"name":"list_github_prs","description":"List GitHub pull requests with filters for state. Returns JSON with PR number, title, author, review status, and dates.","parameters":"[{\"name\":\"repo\",\"type\":\"string\",\"description\":\"Repository in owner/name format\",\"required\":true},{\"name\":\"state\",\"type\":\"string\",\"description\":\"PR state: open, closed, merged, or all\",\"required\":true},{\"name\":\"limit\",\"type\":\"number\",\"description\":\"Maximum number of PRs to return\",\"required\":false}]","scriptTemplate":"botdo gh pr list --repo {{repo}} --state {{state}} --limit {{limit}} --json number,title,author,createdAt,updatedAt,state,reviewDecision,isDraft"},{"name":"post_github_comment","description":"Post a comment on a GitHub issue. The comment body is written to a temp file to avoid shell quoting issues.","parameters":"[{\"name\":\"repo\",\"type\":\"string\",\"description\":\"Repository in owner/name format\",\"required\":true},{\"name\":\"issue_number\",\"type\":\"number\",\"description\":\"Issue number\",\"required\":true},{\"name\":\"body\",\"type\":\"string\",\"description\":\"Comment body (markdown)\",\"required\":true}]","scriptTemplate":"botdo gh issue comment {{issue_number}} --repo {{repo}} --body-file {{body_file}}"}],"toolsets":[{"name":"Read-Only Tools","description":"Read-only file and git tools for analysis tasks","tools":"Read,Glob,Grep,Bash(ls *),Bash(cat *),Bash(head *),Bash(tail *),Bash(find *),Bash(wc *),Bash(file *),Bash(git log *),Bash(git diff *),Bash(git show *),Bash(git status *),Bash(git branch *)"},{"name":"Read + MCP Tools","description":"Read-only tools plus MCP tools for commenting and labeling","tools":"@Read-Only Tools,mcp__axiom-tools__post_github_comment,mcp__axiom-tools__list_github_labels,mcp__axiom-tools__apply_github_labels"},{"name":"Write Tools","description":"Full read/write tools plus git and MCP tools for implementation tasks","tools":"@Read-Only Tools,Edit,Write,Bash(git add *),Bash(git commit *),Bash(git checkout *),Bash(git switch *),Bash(git push *),Bash(git merge *),Bash(mkdir *),Bash(cp *),Bash(mv *),mcp__axiom-tools__post_github_comment,mcp__axiom-tools__create_github_pr"}],"actionTypes":[{"name":"analyze","description":"Read and understand an issue, assess complexity, and identify affected components. Use this action when an issue is complex enough to require a full structured analysis with issue summary, findings, complexity assessment, and recommended next steps. This is a read-only action — no code changes are made.","executionMode":"actor","userTriggerable":true,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Read-Only Tools","promptTemplate":"You are analyzing a GitHub issue. Read the issue details and produce a structured analysis. \n\n## Instructions\n1. Read and understand the issue described below\n2. If you need to examine the code, clone the repository first:    git clone https://github.com/{{repository}}.git {{workDir}}/repo\n3. Analyze the issue according to the instructions from the oss-issues skill. \n4. Do NOT make any code changes — this is a read-only analysis\n5. Post the analysis as a comment on the GitHub issue\n6. Remove the needs-analyzis label and add the needs-implementation label\n7. You MUST use the botdo wrapper command to invoke any github CLI command (i.e.: botdo gh issue comment 123 --body \"Message\")\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Work Directory\n{{workDir}}\n\n## Context from Manager\n{{managerInput}}\n"},{"name":"answer-question","description":"Answer a question asked by a user on a GitHub issue. Use this when the issue body or a comment contains a question (indicated by question marks, 'how do I', 'what is', etc.). The actor examines the repository to find the answer and posts it as a comment on the issue. Can be triggered directly from issue-created events when the issue is clearly a question.","executionMode":"actor","userTriggerable":false,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Read + MCP Tools","promptTemplate":"You are answering a question on a GitHub issue.\n\n## Instructions\n1. Read the question described below\n2. Examine the repository to find the answer\n3. Post your answer directly on the issue using the post_github_comment tool with the repository, issue number, and your answer as the body\n4. Keep your answer concise, friendly, and informative\n5. If you cannot post the comment, include the full answer in your output\n6. You MUST use the botdo wrapper command to invoke any github CLI command (i.e.: botdo gh issue comment {{issueRef}} --body \"Message\")\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Context from Manager\n{{managerInput}}\n"},{"name":"auto-tag","description":"Determine and apply appropriate labels/tags to a GitHub issue. Use this when a new issue is created and needs categorization (e.g. bug, feature, documentation, question, good-first-issue).","executionMode":"actor","userTriggerable":false,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Read + MCP Tools","promptTemplate":"You are tagging a GitHub issue with appropriate labels.\n\n## Instructions\n1. Read the issue title and body\n2. Use the list_github_labels tool to discover which labels are available in the repository\n3. Choose the most appropriate labels from the available list based on the issue content\n4. Use the apply_github_labels tool to apply the chosen labels to the issue\n5. If no suitable labels exist in the repository, skip labeling and report what labels you would have applied\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Context from Manager\n{{managerInput}}\n"},{"name":"close-project","description":"Mark the project as completed. Use this script action when an issue-closed event is received, indicating the issue has been resolved and the project should be marked as done.","executionMode":"script","userTriggerable":true,"managerTriggerable":true,"emitsEvent":false,"scriptTemplate":"#!/bin/bash\ncurl -s -X POST \"{{apiBaseUrl}}/projects/{{projectId}}/close\"\n"},{"name":"implement","description":"Write code to address the issue by creating a feature branch, making changes, and opening a pull request. Use this when an analysis has been completed and the issue requires code changes (bug fixes or feature implementations). Should not be triggered directly from an incoming event — typically follows a completed 'analyze' or 'propose' task.","executionMode":"actor","userTriggerable":true,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Write Tools","promptTemplate":"You are implementing a code change to address a GitHub issue.\n\n## Instructions\n1. Clone the repository:    git clone https://github.com/{{repository}}.git {{workDir}}/repo    && cd {{workDir}}/repo\n2. Read the issue and understand what needs to be done\n3. Examine the codebase\n4. Implement the issue according to the instructions from the oss-issue skill.\n5. Always open the pull request as a draft.\n6. After opening the PR, remove the needs-implementation label.\n7. 6. You MUST use the botdo wrapper command to invoke any github CLI command (i.e.: botdo gh issue comment {{issueRef}} --body \"Message\")\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Work Directory\n{{workDir}}\n\n## Context from Manager\n{{managerInput}}\n"},{"name":"propose","description":"Draft a proposal or design document for addressing a complex issue. Use this for issues that require architectural decisions or significant changes before implementation begins. Produces a design proposal with approach, files to change, risks, and estimated effort. Read-only — no code changes are made.","executionMode":"actor","userTriggerable":true,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Read-Only Tools","promptTemplate":"You are drafting a proposal for how to address a GitHub issue.\n\n## Instructions\n1. Read the issue and understand the requirements\n2. If you need to examine the code, clone the repository first:    git clone https://github.com/{{repository}}.git {{workDir}}/repo\n3. Produce a design proposal with:\n   - **Approach**: How you would solve this\n   - **Files to Change**: Which files would be modified\n   - **Risks**: Potential issues or trade-offs\n   - **Estimated Effort**: Rough assessment of complexity\n4. Do NOT make any code changes — this is a read-only proposal\n5. You MUST use the botdo wrapper command to invoke any github CLI command (i.e.: botdo gh issue comment {{issueRef}} --body \"Message\")\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Work Directory\n{{workDir}}\n\n## Context from Manager\n{{managerInput}}\n"},{"name":"reopen-project","description":"Re-open a completed project. Use this script action when an issue-reopened event is received, indicating the issue needs further attention after being previously closed.","executionMode":"script","userTriggerable":true,"managerTriggerable":true,"emitsEvent":false,"scriptTemplate":"#!/bin/bash\ncurl -s -X POST \"{{apiBaseUrl}}/projects/{{projectId}}/reopen\"\n"},{"name":"respond","description":"Reply to a comment or review feedback on a GitHub issue or pull request. Use this when a previous task failed to post its findings, or when review feedback requires a follow-up response with code changes. Can make code changes and post comments.","executionMode":"actor","userTriggerable":true,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Write Tools","promptTemplate":"You are responding to feedback on a GitHub issue or pull request.\n\n## Instructions\n1. If you need to work with the code, clone the repository first:    git clone https://github.com/{{repository}}.git {{workDir}}/repo    && cd {{workDir}}/repo\n2. Read the feedback or comment described below\n3. If code changes are requested, make them according to the instructions from the oss-review skill.\n4. Post a response on the issue:\n   a. Write your comment to /tmp/gh-comment.md using the Write tool\n   b. Then run: botdo gh issue comment <number> --repo {{repository}} --body-file /tmp/gh-comment.md\n5. If you cannot post the comment, include the full response text in your output\n6. You MUST use the botdo wrapper command to invoke any github CLI command (i.e.: botdo gh issue comment {{issueRef}} --body \"Message\")\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Work Directory\n{{workDir}}\n\n## Context from Manager\n{{managerInput}}\n"},{"name":"review","description":"Review a pull request or code change for correctness, style, and potential issues. Use this when a PR is opened or updated, or when an 'implement' task has been completed and the resulting code needs review. Read-only — produces a review summary but does not modify code.","executionMode":"actor","userTriggerable":true,"managerTriggerable":true,"emitsEvent":true,"allowedTools":"@Read-Only Tools","promptTemplate":"You are reviewing code changes related to a GitHub issue.\n\n## Instructions\n1. If you need to examine the code, clone the repository first:    git clone https://github.com/{{repository}}.git {{workDir}}/repo\n2. Examine the changes\n3. Review for correctness, style, and potential issues\n4. Produce a review summary with:\n   - **Summary**: What the changes do\n   - **Issues Found**: Any bugs, style issues, or concerns\n   - **Suggestions**: Improvements or alternatives\n5. Do NOT make any code changes\n6. You MUST use the botdo wrapper command to invoke any github CLI command (i.e.: botdo gh issue comment {{issueRef}} --body \"Message\")\n\n## Issue\n{{issueRef}} in {{repository}}\n\n## Work Directory\n{{workDir}}\n\n## Context from Manager\n{{managerInput}}\n"}]}