├── .github └── workflows │ ├── generate_automation.yml │ ├── generate_tool.yml │ ├── generate_workflow_documentation.yaml │ ├── import_smart_workflow.yaml │ ├── plan_and_execute.yaml │ ├── quick_code_change.yml │ └── quick_task.yaml ├── .gitignore ├── LICENSE ├── README.md ├── automations ├── chat-bot │ ├── README.md │ └── workflow.yaml ├── enforce-contribution-guidelines │ ├── README.md │ └── workflow.yaml ├── format-issue │ ├── README.md │ └── workflow.yaml ├── help-with-documentation │ ├── README.md │ └── workflow.yaml ├── help-with-implementation │ ├── README.md │ └── workflow.yaml ├── investigate-bug │ ├── README.md │ └── workflow.yaml ├── pr-auto-review │ ├── README.md │ └── workflow.yaml ├── product-owner │ ├── README.md │ └── workflow.yaml ├── refine-issue │ ├── README.md │ └── workflow.yaml └── work-on-todo-list │ ├── README.md │ └── workflow.yaml ├── index.yaml └── tools ├── answer-question ├── README.md └── workflow.yaml ├── draw-diagram ├── README.md └── workflow.yaml ├── generate-automation ├── README.md └── workflow.yaml ├── generate-tool ├── README.md └── workflow.yaml ├── import-workflow ├── README.md └── workflow.yaml ├── initialize-project ├── README.md └── workflow.yaml ├── quick-code-change ├── README.md └── workflow.yaml ├── quick-task ├── README.md └── workflow.yaml ├── write-technical-specification ├── README.md └── workflow.yaml └── write-user-story ├── README.md └── workflow.yaml /.github/workflows/generate_automation.yml: -------------------------------------------------------------------------------- 1 | name: "🧙‍♂️ Generate Automation" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | automation-name: 7 | description: 'Name of the automation' 8 | required: true 9 | trigger: 10 | description: 'What should trigger the automation?' 11 | required: true 12 | goal: 13 | description: 'What should the automation accomplish when it is triggered?' 14 | required: true 15 | 16 | jobs: 17 | create-new-automation: 18 | runs-on: ubuntu-latest 19 | steps: 20 | - name: Create New Automation 21 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 22 | with: 23 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 24 | agent-instructions: | 25 | Your task is to generate a new Github workflow. 26 | The workflow's purpose is to have an AI agent respond to a given trigger in the repository. 27 | 28 | The workflow should be called `${{ github.event.inputs.automation-name }}`. 29 | 30 | It should be triggered when: 31 | **${{ github.event.inputs.trigger }}** 32 | 33 | When triggered, the user workflow should accomplish the following goal: 34 | **${{ github.event.inputs.goal }}** 35 | 36 | The workflow file must fulfill the following criteria: 37 | - Name of the workflow starts with an emoji (UTF-8 character) 38 | - Has only one job with at least one step that uses `PR-Pilot-AI/smart-actions/quick-task@v1` 39 | - The step should have the following inputs: 40 | - `api-key` (similar to reference workflow) 41 | - `agent-instructions` (Step-by-step instructions for the AI agent) 42 | 43 | If the agent's task requires data from the workflow run (e.g. issue ID, commit msg, etc), 44 | or output from previous steps, then the text for `agent-instructions` should have these values injected 45 | into them using the github context variables. 46 | 47 | The agent instructions need to be an actionable step-by-step guide for the AI agent to follow. 48 | Make sure the step-by-step instructions are clear and concise. 49 | 50 | Assume that the agent has the same capabilities as you do. It is important to only include 51 | instructions that are within the agent's capabilities. 52 | 53 | Do the following: 54 | 1. Read `automations/investigate-bug/workflow.yaml` as reference to understand the desired structure of the workflow file. 55 | 2. Turn the workflow goal provided by the user into job steps and actionable step-by-step instructions for the AI agent. 56 | 3. Generate the new Github workflow file in `automations//workflow.yaml` 57 | 4. Read `automations/investigate-bug/README.md` as reference to understand the desired structure of the README file for the workflow. 58 | 5. Generate the new README file in `automations//README.md` 59 | 6. Add the automation to `index.yaml` with the appropriate details 60 | 7. Add the automation to the README.md file with the appropriate details 61 | -------------------------------------------------------------------------------- /.github/workflows/generate_tool.yml: -------------------------------------------------------------------------------- 1 | name: "🧙‍♂️ Generate Tool" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | tool-name: 7 | description: 'Name of the tool' 8 | required: true 9 | tool-inputs: 10 | description: 'Inputs required for the tool' 11 | required: true 12 | agent-instructions: 13 | description: 'What should the agent do when the tool is executed?' 14 | required: true 15 | template-tool: 16 | description: 'ID of the tool to be used as example' 17 | required: true 18 | default: 'quick-code-change' 19 | 20 | jobs: 21 | automate-tool-creation: 22 | runs-on: ubuntu-latest 23 | steps: 24 | - name: Automate Tool Creation 25 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 26 | with: 27 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 28 | agent-instructions: | 29 | Your task is to generate a new Github workflow. 30 | The workflow's purpose is to serve as a tool for the user to interact with an AI agent 31 | that can operate on the repository. 32 | 33 | The workflow should be called `${{ github.event.inputs.tool-name }}`. 34 | 35 | It should have the following inputs: 36 | ``` 37 | ${{ github.event.inputs.tool-inputs }} 38 | ``` 39 | 40 | When triggered, the user wants the agent to do the following with the given inputs: 41 | ``` 42 | ${{ github.event.inputs.agent-instructions }} 43 | ``` 44 | 45 | These instructions need to be turned into an actionable step-by-step guide for the AI agent to follow. 46 | Make sure the step-by-step instructions are clear and concise. 47 | 48 | Assume that the agent has the same capabilities as you do. It is important to only include 49 | instructions that are within the agent's capabilities. 50 | 51 | The workflow file must fulfill the following criteria: 52 | - Name of the workflow starts with an emoji (UTF-8 character) 53 | - Has only one job with one step that uses `PR-Pilot-AI/smart-actions/quick-task@v1` 54 | - The step should have the following inputs: 55 | - `api-key` (similar to reference workflow) 56 | - `agent-instructions` (Step-by-step instructions for the AI agent) 57 | 58 | If the agent's task requires data from the workflow run (e.g. issue ID, commit msg, etc), 59 | then the text for `agent-instructions` should have these values injected into them using the 60 | github context variables. 61 | 62 | Do the following: 63 | 1. Read `tools/${{ github.event.inputs.template-tool }}/workflow.yaml` as reference to understand the desired structure of the workflow file. 64 | 2. Turn the free-text instructions provided by the user into actionable step-by-step instructions for the AI agent. 65 | 3. Generate the new Github workflow file in `tools//workflow.yaml` 66 | 4. Read `tools/${{ github.event.inputs.template-tool }}/README.md` as reference to understand the desired structure of the README file for the workflow. 67 | 5. Generate the new README file in `tools//README.md` 68 | 6. Add the tool to `index.yaml` with the appropriate details 69 | 7. Add the tool to the README.md file with the appropriate details -------------------------------------------------------------------------------- /.github/workflows/generate_workflow_documentation.yaml: -------------------------------------------------------------------------------- 1 | name: "🚀 Generate Workflow Documentation" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | workflow: 7 | description: 'Which workflow needs documentation?' 8 | required: true 9 | 10 | jobs: 11 | execute_quick_task: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Document Workflow 15 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 16 | with: 17 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 18 | agent-instructions: | 19 | 1. Look at `tools/quick-task/README.md` to see how the README file for the workflow should be structured. 20 | 2. Read the workflow file `tools/${{ github.event.inputs.workflow }}/workflow.yaml` to understand the workflow. 21 | 3. Create a README file in `tools/${{ github.event.inputs.workflow }}/README.md` similar to the one you read in step 1. 22 | 4. Make sure the tool is listed in `index.yaml` and `README.md`. 23 | -------------------------------------------------------------------------------- /.github/workflows/import_smart_workflow.yaml: -------------------------------------------------------------------------------- 1 | name: 🔄 Import Smart Workflow 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | workflow-id: 7 | description: ID of the workflow to import 8 | required: true 9 | 10 | jobs: 11 | setup: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Checkout PR-Pilot-AI/smart-workflows 15 | uses: actions/checkout@v2 16 | with: 17 | repository: PR-Pilot-AI/smart-workflows 18 | token: ${{ secrets.GITHUB_TOKEN }} 19 | - name: Determine workflow file path 20 | id: filepath 21 | run: | 22 | if [ -f tools/${{ github.event.inputs.workflow-id }}/workflow.yaml ]; then 23 | echo "::set-output name=path::tools/${{ github.event.inputs.workflow-id }}/workflow.yaml" 24 | elif [ -f automations/${{ github.event.inputs.workflow-id }}/workflow.yaml ]; then 25 | echo "::set-output name=path::automations/${{ github.event.inputs.workflow-id }}/workflow.yaml" 26 | else 27 | echo "Path not found" && exit 1 28 | fi 29 | - name: Copy workflow file 30 | id: print-workflow 31 | run: | 32 | workflow=$(cat ${{ steps.filepath.outputs.path }}) 33 | echo "WORKFLOW<> "$GITHUB_OUTPUT" 34 | 35 | - name: Import Workflow 36 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 37 | with: 38 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 39 | agent-instructions: | 40 | Create a new file in `.github/workflows/` for the following workflow: 41 | 42 | --- 43 | 44 | ${{ steps.print-workflow.outputs.WORKFLOW }} 45 | 46 | --- 47 | 48 | The user can customize the workflow by instructing you using `/pilot ` in a comment. 49 | Read the `README.md` file to learn more about the project, then respond to the user with a few customization 50 | prompt suggestions tailored to this project. The prompts must be short instructions that you will be 51 | able to interpret and execute. -------------------------------------------------------------------------------- /.github/workflows/plan_and_execute.yaml: -------------------------------------------------------------------------------- 1 | name: "🚀 Plan and Execute" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | high-level-task: 7 | description: 'What should the agent plan and execute?' 8 | required: true 9 | goal: 10 | description: 'What is the goal of the task?' 11 | required: true 12 | 13 | jobs: 14 | execute-and-plan: 15 | runs-on: ubuntu-latest 16 | steps: 17 | - name: Create a step-by-step plan 18 | id: create-plan 19 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 20 | with: 21 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 22 | sdk-version: 1.3.1 23 | agent-instructions: | 24 | The user wants you to create a step-by-step plan for the following: 25 | 26 | ``` 27 | ${{ github.event.inputs.high-level-task }} 28 | ``` 29 | 30 | The goal of the task is: 31 | ${{ github.event.inputs.goal }} 32 | 33 | The plan will later be executed by you, so make sure it is within your capabilities. 34 | The plan should: 35 | - Be clear and concise and use imperative language 36 | 37 | The following should NOT be part of the plan: 38 | - Any action that requires user input 39 | - Any action that requires executing scripts or code 40 | - Any action that requires testing or validation 41 | 42 | Create the plan. 43 | - name: Execute the plan 44 | id: execute-plan 45 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 46 | with: 47 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 48 | sdk-version: 1.3.1 49 | agent-instructions: | 50 | We have the following step-by-step plan for you to execute: 51 | 52 | ${{ steps.create-plan.outputs.task-result }} 53 | 54 | The goal of the task is: 55 | ${{ github.event.inputs.goal }} 56 | 57 | Execute the plan to achieve the goal. 58 | -------------------------------------------------------------------------------- /.github/workflows/quick_code_change.yml: -------------------------------------------------------------------------------- 1 | name: "🛠 Quick Code Change" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | code-to-change: 7 | description: 'Specify the code or file to change.' 8 | required: true 9 | how-to-change-it: 10 | description: 'Describe how to change the code.' 11 | required: true 12 | 13 | jobs: 14 | execute_code_change: 15 | runs-on: ubuntu-latest 16 | steps: 17 | - name: Execute Code Change 18 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 19 | with: 20 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 21 | agent-instructions: | 22 | Read the following code: 23 | ${{ inputs.code-to-change }} 24 | 25 | and change it in the following way: 26 | ${{ inputs.how-to-change-it }} 27 | -------------------------------------------------------------------------------- /.github/workflows/quick_task.yaml: -------------------------------------------------------------------------------- 1 | name: "🚀 Quick Task" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | agent-instructions: 7 | description: 'What should the agent do for you?' 8 | required: true 9 | 10 | jobs: 11 | execute_quick_task: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Execute AI Task 15 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 16 | with: 17 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 18 | agent-instructions: ${{ github.event.inputs.agent-instructions }} 19 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .idea 2 | *.iml 3 | venv -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 |
2 | PR Pilot Logo 3 |
4 |

5 | Install | 6 | Documentation | 7 | Blog | 8 | Website 9 |

10 | 11 | # Smart Workflows 12 | 13 | This is a repository for **agentic Github workflows** that use an AI agent 14 | to automate Github projects in powerful ways. 15 | 16 | * **Plug-and-play** - Works out-of-the box, just copy YAML files 17 | * **Fully Customizable** using natural language instructions. 18 | * **LLM Best Practices** baked in, so you can focus on what matters 19 | 20 | To use them in your project: 21 | 22 | 1. **[Install the AI agent](https://github.com/apps/pr-pilot-ai/installations/new)** on your repository 23 | 2. Add the **[🔄 Import Workflow](tools/import-workflow)** tool to your project 24 | 3. Use the tool to import any workflow you like 25 | 26 | That's it! 27 | 28 | ## Plug-and-Play Workflows 29 | 30 | Smart Workflows come in two flavors **Automations** and **Tools**. 31 | 32 | ### Automations 33 | 34 | Workflows that run automatically in response to [Github events](https://docs.github.com/en/rest/using-the-rest-api/github-event-types?apiVersion=2022-11-28) 35 | 36 | | Name | Description | 37 | |------------------------------------------------------------|--------------------------------------------------------------------------------------------------------| 38 | | **[🤖 Chat Bot](automations/chat-bot)** | Turn any Github issue into a conversation with your AI agent by adding the `chat` label | 39 | | **[📝 Format and Label New Issues](automations/format-issue)** | Automatically format and label every new issue created in your project | 40 | | **[🔍 PR Auto Review](automations/pr-auto-review)** | Every new PR will be reviewed by an AI Agent according to your preferences | 41 | | **[🐞 Investigate Bug](automations/investigate-bug)** | Automatically investigates issues labeled as `bug` by analyzing the codebase and providing suggestions | 42 | | **[📚 Help with Documentation](automations/help-with-documentation)** | Automatically assists with documentation tasks when the `needs-documentation` label is added to an issue | 43 | | **[🔍 Refine Issue](automations/refine-issue)** | Automatically refines issues labeled with `needs-refinement` by analyzing the issue description, searching the codebase for related files, and enhancing the issue with relevant context and acceptance criteria | 44 | | **[🛠 Help with Implementation](automations/help-with-implementation)** | Automatically assists with implementation tasks when the `needs-work` label is added to an issue by reading the issue, understanding the requirements, searching for related files, and writing the necessary changes | 45 | | **[📐 Enforce Contribution Guidelines](automations/enforce-contribution-guidelines)** | Automatically ensures that new pull requests adhere to the project's contribution guidelines | 46 | | **[📋 Work on TODO List](automations/work-on-todo-list)** | Automatically works on items listed in the TODO.md file when updated on the main branch. If all items are completed, it deletes the TODO.md file. | 47 | | **[👩‍💼 Product Owner](automations/product-owner)** | Acts as a virtual Product Owner, modifying issues labeled with `feature-request` to include structured sections for user story, functional and non-functional requirements, and out of scope. | 48 | 49 | ### Tools 50 | 51 | Workflows for you to run manually via the Github Actions tab in your repository. 52 | 53 | | Name | Description | 54 | | ---- |----------------------------------------------| 55 | | **[🚀 Quick Task](tools/quick-task)** | Instruct the agent to do something for you in your own words | 56 | | **[🤖 Answer Question](tools/answer-question)** | Ask a question about your project / code | 57 | | **[🧙‍♂️ Generate Automation](tools/generate-automation)** | Generate custom automations tailored to your project | 58 | | **[🧙‍♂️ Generate Tool](tools/generate-tool)** | Generate custom tools tailored to your project | 59 | | **[🔄 Import Workflow](tools/import-workflow)** | One-click solution for adding Smart Workflows to your project | 60 | | **[🛠 Quick Code Change](tools/quick-code-change)** | Facilitate quick code modifications through an AI agent based on user inputs | 61 | | **[✍️ Write User Story](tools/write-user-story)** | Generate comprehensive user stories for your code base | 62 | | **[✍️ Write Technical Specification](tools/write-technical-specification)** | Generates technical specifications based on user stories through an AI agent | 63 | | **[📊 Draw Diagram](tools/draw-diagram)** | Generate Mermaid diagrams based on the repository's code and files | 64 | | **[🚀 Initialize Project](tools/initialize-project)** | Assist users in setting up a new project by generating a Github issue with concise, actionable instructions and a list of files to be created, based on the specified programming language and optional framework | 65 | 66 | ### Contributing 67 | 68 | If you'd like to contribute workflows, simply: 69 | 70 | 1. Fork the project 71 | 2. Run the **[🧙‍♂️ Generate Automation](tools/generate-automation)** or **[🧙‍♂️ Generate Tool](tools/generate-tool)** workflows 72 | 3. Customize the code the agent generated for you in a PR and merge it 73 | 4. Open a PR to this project 74 | 75 | -------------------------------------------------------------------------------- /automations/chat-bot/README.md: -------------------------------------------------------------------------------- 1 | # 🤖 Chat Bot Automation 2 | 3 | **ID**: `chat-bot` 4 | 5 | This automation enables you to turn any Github issue into a conversation with your AI agent by providing automated responses to comments on issues labeled with `chat`. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when an issue is labeled or commented on, and also when a comment is created on an issue. 10 | - **Label Requirement:** The issue must be labeled with `chat` for the automation to respond. 11 | - **Exclusion:** The automation ignores actions initiated by `pr-pilot-ai[bot]` to prevent loops. 12 | 13 | ## How to Use 14 | 15 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 16 | 2. Label an issue with `chat` or comment on an issue already labeled with `chat`. 17 | 3. The automation will respond to comments under the conditions specified above. 18 | 19 | ## Customization Ideas 20 | 21 | - Customize the `agent-instructions` within the workflow to tailor the chat bot's responses based on the issue's content or the nature of the comments. 22 | - Adjust the trigger conditions to include more types of interactions or to narrow down the scope to very specific actions. 23 | 24 | This automation provides a basic framework for engaging with users or contributors in a more interactive manner, making the issue handling process feel more personal and dynamic. 25 | 26 | ```mermaid 27 | graph TD; 28 | A[Issue Created/Commented] -->|Labeled with 'chat'| B[Automation Triggered]; 29 | B --> C{Is it a bot comment?}; 30 | C -->|No| D[Respond to Comment]; 31 | C -->|Yes| E[Ignore]; 32 | ``` 33 | -------------------------------------------------------------------------------- /automations/chat-bot/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🤖 Chat Bot" 2 | 3 | on: 4 | issues: 5 | types: [labeled, commented] 6 | issue_comment: 7 | types: [created] 8 | 9 | jobs: 10 | handle-chat: 11 | if: > 12 | (github.event.label.name == 'chat' || contains(github.event.issue.labels.*.name, 'chat')) && 13 | github.event.sender.login != 'pr-pilot-ai[bot]' 14 | runs-on: ubuntu-latest 15 | steps: 16 | - name: AI Chat Response 17 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 18 | with: 19 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 20 | agent-instructions: | 21 | @${{ github.event.sender.login }} commented on issue #${{ github.event.issue.number }}. 22 | Read the content of issue #${{ github.event.issue.number }}. 23 | If there are no comments yet, add a comment that makes sense in the context of the issue. 24 | If there are comments, provide a response to the latest comment. 25 | -------------------------------------------------------------------------------- /automations/enforce-contribution-guidelines/README.md: -------------------------------------------------------------------------------- 1 | # 📐 Enforce Contribution Guidelines Automation 2 | 3 | **ID**: `enforce-contribution-guidelines` 4 | 5 | This automation is designed to ensure that all new pull requests adhere to the project's contribution guidelines as outlined in the `CONTRIBUTING.md` file. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when a new pull request is opened. 10 | - **Verification Process:** The automation reads the `CONTRIBUTING.md` file to understand the contribution guidelines, then reads the newly opened pull request to determine if it follows these guidelines. 11 | - **Outcome:** If the pull request does not follow the guidelines, the automation will comment on the pull request explaining which parts of the guidelines were not followed. 12 | 13 | ```mermaid 14 | graph TD; 15 | A[New Pull Request Opened] --> B[Automation Triggered]; 16 | B --> C[Read CONTRIBUTING.md]; 17 | C --> D[Read Pull Request]; 18 | D --> E[Verify Against Guidelines]; 19 | E --> F[Comment on PR if Guidelines Not Followed]; 20 | ``` 21 | 22 | ## How to Use 23 | 24 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 25 | 2. Open a new pull request. 26 | 3. The automation will verify the pull request against the contribution guidelines and comment if any discrepancies are found. 27 | 28 | ## Customization Ideas 29 | 30 | - Customize the `agent-instructions` within the workflow to tailor the verification process based on the specific needs of your project or the nature of contributions expected. -------------------------------------------------------------------------------- /automations/enforce-contribution-guidelines/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "📐 Enforce Contribution Guidelines" 2 | 3 | # Triggers the workflow when a new pull request is created 4 | on: 5 | pull_request: 6 | types: [opened] 7 | 8 | jobs: 9 | enforce-guidelines: 10 | runs-on: ubuntu-latest 11 | steps: 12 | - name: Check PR Against Contribution Guidelines 13 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 14 | with: 15 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 16 | agent-instructions: | 17 | 1. Read `CONTRIBUTING.md` to understand the contribution guidelines. 18 | 2. Read the PR with ID `${{ github.event.pull_request.number }}` to understand its content and intent. 19 | 3. If the PR follows the contribution guidelines, do nothing. 20 | 4. Otherwise, comment on the PR explaining which parts of the contribution guidelines were not followed. -------------------------------------------------------------------------------- /automations/format-issue/README.md: -------------------------------------------------------------------------------- 1 | # 📝 Format and Label New Issues 2 | 3 | **ID**: `format-issue` 4 | 5 | This automation listens for new issues created in your repository and automatically formats the issue body and adds labels based on the issue title. 6 | 7 | 8 | ```mermaid 9 | graph TD; 10 | A[New Issue Created] --> B[Automation Triggered]; 11 | B --> C[Format Issue Body]; 12 | B --> D[Add Labels Based on Title]; 13 | ``` 14 | 15 | 16 | ## How to Use 17 | 18 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 19 | 2. Open a new issue in your repository and see the magic happen! 20 | 21 | ## Customization Ideas 22 | 23 | Use your own words in `formatting-instructions` to describe how you'd like the issue formatted and labeled. 24 | 25 | Here are some ideas for what you could say: 26 | 27 | * Issue titles must always begin with an Emoji 28 | * Issues labeled with `feature-request` must always contain a checklist of acceptance criteria 29 | * Issues labeled with `bug` must always contain a code snippet that reproduces the bug 30 | * Any file name should be turned into Markdown links to the file in the repository 31 | 32 | Your imagination is the limit! 33 | -------------------------------------------------------------------------------- /automations/format-issue/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "📝 Format and Label New Issues" 2 | 3 | # Triggers the workflow on new issue creation 4 | on: 5 | issues: 6 | types: [opened] 7 | 8 | jobs: 9 | format-issue: 10 | runs-on: ubuntu-latest 11 | outputs: 12 | task-url: ${{ steps.format.outputs.task-url }} 13 | steps: 14 | - name: Format GitHub Issue 15 | id: format 16 | uses: PR-Pilot-AI/smart-actions/format-issue@v1 17 | with: 18 | 19 | # API key for PR Pilot must be defined as a secret in the repository 20 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 21 | 22 | # Number of the issue to be formatted 23 | issue-number: ${{ github.event.issue.number }} 24 | 25 | # Instructions for formatting the issue 26 | formatting-instructions: | 27 | All issues should be properly Markdown-formatted: 28 | * File paths and code identifiers should be enclosed in backticks 29 | * Code blocks should be enclosed in triple backticks 30 | * Issue titles should be concise, descriptive and start with an appropriate emoji (UTF-8 character) 31 | 32 | Every issue should have at least one label. Only the following labels are allowed: 33 | * `bug` - for bugs 34 | * `enhancement` - for feature requests 35 | * `question` - for questions 36 | * `documentation` - for documentation-related tasks 37 | 38 | It is IMPORTANT that you do not alter the existing content of the issue body, only the formatting. 39 | 40 | -------------------------------------------------------------------------------- /automations/help-with-documentation/README.md: -------------------------------------------------------------------------------- 1 | # 📚 Help with Documentation Automation 2 | 3 | **ID**: `help-with-documentation` 4 | 5 | This automation assists in enhancing project documentation by responding to issues labeled with `needs-documentation`. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is activated when an issue is labeled with `needs-documentation`. 10 | - **Action:** Upon triggering, the automation analyzes the issue to understand the documentation needs. Depending on the requirements, it may directly update documentation files in the repository or compile documentation advice and post it as a comment on the issue. 11 | 12 | ```mermaid 13 | graph TD; 14 | A[Issue Labeled with 'needs-documentation'] --> B[Automation Triggered]; 15 | B --> C[Analyze Issue for Documentation Needs]; 16 | C --> D[Update Documentation/Post Advice]; 17 | ``` 18 | 19 | 20 | ## How to Use 21 | 22 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 23 | 2. Label an issue with `needs-documentation`. 24 | 3. The automation will assess the issue and take appropriate action to aid in documentation, either by updating files or providing guidance through comments. 25 | 26 | ## Customization Ideas 27 | 28 | - Tailor the `agent-instructions` within the workflow to better suit your project's documentation standards and practices. 29 | - Modify the trigger conditions to include more specific scenarios or additional types of documentation requests. 30 | 31 | This automation streamlines the process of improving and updating project documentation, making it easier to maintain high-quality, comprehensive documentation. 32 | -------------------------------------------------------------------------------- /automations/help-with-documentation/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "📚 Help with Documentation" 2 | 3 | # Triggers the workflow when a label `needs-documentation` is added to an issue 4 | on: 5 | issues: 6 | types: [labeled] 7 | 8 | jobs: 9 | documentation-help: 10 | runs-on: ubuntu-latest 11 | if: github.event.label.name == 'needs-documentation' 12 | steps: 13 | - name: Provide Documentation Help 14 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 15 | with: 16 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 17 | agent-instructions: | 18 | 1. Read the issue with ID `${{ github.event.issue.number }}`. 19 | 2. Analyze the issue content to understand what needs to be documented. 20 | 3. If the documentation is file-based and can be added to the repository, use `functions.write_file` to create or update the necessary files. 21 | 4. If the documentation cannot be directly added to the repository, compile documentation snippets and post them as a comment on the issue. 22 | -------------------------------------------------------------------------------- /automations/help-with-implementation/README.md: -------------------------------------------------------------------------------- 1 | # 🛠 Help with Implementation Automation 2 | 3 | **ID**: `help-with-implementation` 4 | 5 | This automation is designed to assist with the implementation tasks when an issue is labeled with `needs-work`. It automatically reads the issue, understands the requirements, searches the codebase for related files, and writes the necessary changes to the files. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when an issue is labeled with `needs-work`. 10 | - **Implementation Process:** The automation reads the issue, analyzes the description to understand what needs to be worked on, searches the codebase for related files, reads the identified files, and writes the necessary changes to the files. 11 | - **Output:** It commits the changes with a message that includes the issue ID and a brief description of the work done. 12 | 13 | ```mermaid 14 | graph TD; 15 | A[Issue Labeled with 'needs-work'] --> B[Automation Triggered]; 16 | B --> C[Read and Analyze Issue]; 17 | C --> D[Search Codebase for Related Files]; 18 | D --> E[Write Necessary Changes to Files]; 19 | ``` 20 | 21 | ## How to Use 22 | 23 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 24 | 2. Label an issue with `needs-work`. 25 | 3. The automation will read the issue, understand the requirements, search for related files, and write the necessary changes. 26 | 27 | ## Customization Ideas 28 | 29 | - Customize the `agent-instructions` within the workflow to tailor the implementation process based on the specific needs of your project or the nature of the tasks. 30 | - Adjust the trigger conditions to include more types of interactions or to narrow down the scope to very specific types of tasks. 31 | 32 | This automation provides a structured approach to handling implementation tasks, helping to streamline the process and ensure that necessary changes are made efficiently. -------------------------------------------------------------------------------- /automations/help-with-implementation/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🛠 Help with Implementation" 2 | 3 | # Triggers the workflow when a `needs-work` label is added to an issue 4 | on: 5 | issues: 6 | types: [labeled] 7 | 8 | jobs: 9 | help-with-implementation: 10 | runs-on: ubuntu-latest 11 | if: "github.event.label.name == 'needs-work'" 12 | steps: 13 | - name: Assist with Implementation 14 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 15 | with: 16 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 17 | agent-instructions: | 18 | 1. Read the issue with ID `${{ github.event.issue.number }}`. 19 | 2. Understand what needs to be worked on by analyzing the issue description. 20 | 3. Search the codebase for files related to the issue. 21 | 4. Read the identified files. 22 | 5. Write the necessary changes to the files based on the issue requirements. 23 | 6. Commit the changes with a message that includes the issue ID and a brief description of the work done. -------------------------------------------------------------------------------- /automations/investigate-bug/README.md: -------------------------------------------------------------------------------- 1 | # 🐞 Investigate Bug Automation 2 | 3 | **ID**: `investigate-bug` 4 | 5 | This automation is designed to assist in the initial investigation of issues labeled with `bug` by automatically analyzing the issue description and searching the codebase for related files. It then generates a list of suggestions or recommendations to address the bug. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when an issue is labeled with `bug`. 10 | - **Analysis Process:** The automation reads the issue, analyzes the description for keywords related to the bug, searches the codebase for related files using these keywords, and then reads the identified files. 11 | - **Output:** It generates a list of suggestions or recommendations based on the analysis and comments on the issue with this information. 12 | 13 | 14 | ```mermaid 15 | graph TD; 16 | A[Issue Labeled with 'bug'] --> B[Automation Triggered]; 17 | B --> C[Analyze Issue Description]; 18 | C --> D[Search Codebase for Related Files]; 19 | D --> E[Generate Suggestions/Recommendations]; 20 | ``` 21 | 22 | 23 | ## How to Use 24 | 25 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 26 | 2. Label an issue with `bug`. 27 | 3. The automation will perform an initial investigation and comment on the issue with suggestions or recommendations. 28 | 29 | ## Customization Ideas 30 | 31 | - Customize the `agent-instructions` within the workflow to tailor the investigation process based on the specific needs of your project or the nature of the bugs encountered. 32 | - Adjust the trigger conditions to include more types of interactions or to narrow down the scope to very specific types of bugs. 33 | 34 | This automation provides a structured approach to bug investigation, helping to streamline the initial analysis and suggesting potential fixes or areas for further investigation. 35 | -------------------------------------------------------------------------------- /automations/investigate-bug/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🐞 Investigate Bug" 2 | 3 | # Triggers the workflow when a `bug` label is added to an issue 4 | on: 5 | issues: 6 | types: [labeled] 7 | 8 | jobs: 9 | investigate-bug: 10 | runs-on: ubuntu-latest 11 | if: "github.event.label.name == 'bug'" 12 | steps: 13 | - name: Investigate Bug Issue 14 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 15 | with: 16 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 17 | agent-instructions: | 18 | 1. Read the issue with ID `${{ github.event.issue.number }}`. 19 | 2. Analyze the issue description to identify keywords related to the bug. 20 | 3. Search the codebase for files related to these keywords. 21 | 4. Read the identified files. 22 | 5. Generate a list of suggestions/recommendations based on the issue and the contents of the related files. 23 | 6. Comment on the issue with the list of suggestions/recommendation. 24 | -------------------------------------------------------------------------------- /automations/pr-auto-review/README.md: -------------------------------------------------------------------------------- 1 | # 🔍 Review New Pull Request 2 | 3 | **ID**: `pr-auto-review` 4 | 5 | This automation listens for new pull requests created in your repository and automatically reviews the PR according to your preferences. 6 | 7 | ```mermaid 8 | graph TD; 9 | A[New PR Created] --> B[Automation Triggered]; 10 | B --> C[Review PR According to Preferences]; 11 | ``` 12 | 13 | ## How to Use 14 | 15 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 16 | 2. Open a new PR in your repository and see the magic happen! 17 | 18 | ## Customization Ideas 19 | 20 | Use your own words in `agent-instructions` to describe how you'd like the PR reviewed. 21 | 22 | Here are some ideas for what you could say: 23 | * Ensure code is DRY (Don't Repeat Yourself) 24 | * Check for any security red flags 25 | * Make sure all code has docstrings and use style 26 | * Point out code that could be refactored 27 | * Watch out for code that could lead to GDPR violations 28 | 29 | Your imagination is the limit! 30 | -------------------------------------------------------------------------------- /automations/pr-auto-review/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🔍 Review New Pull Request" 2 | 3 | # Triggers the workflow on new pull request creation 4 | on: 5 | pull_request: 6 | types: [opened] 7 | 8 | jobs: 9 | handle-pr: 10 | runs-on: ubuntu-latest 11 | outputs: 12 | task-url: ${{ steps.review.outputs.task-url }} 13 | steps: 14 | - name: Handle New PR 15 | id: review 16 | uses: PR-Pilot-AI/smart-actions/pr-creation-handler@v1 17 | with: 18 | 19 | # API key for PR Pilot must be defined as a secret in the repository 20 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 21 | 22 | # Number of the PR to be handled 23 | pr-number: ${{ github.event.pull_request.number }} 24 | 25 | # Instructions for handling the PR 26 | agent-instructions: | 27 | # How to review Pull Requests 28 | 29 | When reviewing a PR, check the following: 30 | 31 | ## Code Quality 32 | - Code is well-documented 33 | - Code is well-formatted 34 | - Code is modular and reusable 35 | - If possible, code is tested 36 | 37 | ## PR Description 38 | - is clear and concise 39 | - includes a summary of changes 40 | - (optional) includes a link to the issue that the PR is addressing 41 | 42 | ## Best Practices 43 | - Code follows best practices of the language / framework being used 44 | - Code is DRY (Don't Repeat Yourself) 45 | - Code is SOLID (Single Responsibility Principle, Open/Closed Principle, Liskov Substitution Principle, Interface Segregation Principle, Dependency Inversion Principle) 46 | 47 | # Review Structure & Format 48 | Use the following structure when formulating your review: 49 | 50 | Your changes look . You've , but there is room for improvement in <...>: 51 | - Change in to 52 | - Class could use 53 | - in file could have 54 | - It is best practice to . Consider in 55 | - etc... 56 | 57 | Review the pull request! -------------------------------------------------------------------------------- /automations/product-owner/README.md: -------------------------------------------------------------------------------- 1 | # 👩‍💼 Product Owner Automation 2 | 3 | **ID**: `product-owner` 4 | 5 | This automation acts as a virtual Product Owner for your project. It is triggered when an issue is labeled with `feature-request`. The automation reads the issue, understands the project by reading the `README.md`, and then modifies the issue to include sections for user story, functional and non-functional requirements, and out of scope. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when an issue is labeled with `feature-request`. 10 | - **Modification Process:** The automation reads the issue and the project's `README.md` file. It then modifies the issue to include structured sections for a user story, functional and non-functional requirements, and what is out of scope. 11 | 12 | ```mermaid 13 | graph TD; 14 | A[Issue Labeled with 'feature-request'] --> B[Automation Triggered]; 15 | B --> C[Read Issue & README.md]; 16 | C --> D[Modify Issue with Structured Sections]; 17 | ``` 18 | 19 | ## How to Use 20 | 21 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 22 | 2. Label an issue with `feature-request`. 23 | 3. The automation will modify the issue to include sections for user story, functional and non-functional requirements, and out of scope. 24 | 25 | ## Customization Ideas 26 | 27 | - Customize the `agent-instructions` within the workflow to tailor the modification process based on the specific needs of your project or the nature of the feature requests encountered. -------------------------------------------------------------------------------- /automations/product-owner/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "👩‍💼 Product Owner" 2 | 3 | # Triggers the workflow when a `feature-request` label is added to an issue 4 | on: 5 | issues: 6 | types: [labeled] 7 | 8 | jobs: 9 | product-owner: 10 | runs-on: ubuntu-latest 11 | if: "github.event.label.name == 'feature-request'" 12 | steps: 13 | - name: Act as Product Owner 14 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 15 | with: 16 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 17 | agent-instructions: | 18 | 1. Read the issue with ID `${{ github.event.issue.number }}`. 19 | 2. Read the `README.md` file to understand the project. 20 | 3. Edit the issue to include sections for user story, functional and non-functional requirements, and out of scope. 21 | 4. Add label `needs-refinement` to the issue 22 | -------------------------------------------------------------------------------- /automations/refine-issue/README.md: -------------------------------------------------------------------------------- 1 | # 🔍 Refine Issue Automation 2 | 3 | **ID**: `refine-issue` 4 | 5 | This automation is designed to refine issues that are labeled with `needs-refinement` by automatically analyzing the issue description, searching the codebase for related files, and then enhancing the issue with relevant context and acceptance criteria. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when an issue is labeled with `needs-refinement`. 10 | - **Refinement Process:** The automation reads the issue, analyzes the description for keywords, searches the codebase for related files using these keywords, reads the identified files, and then edits the issue to add relevant context and acceptance criteria. 11 | 12 | ```mermaid 13 | graph TD; 14 | A[Issue Labeled with 'needs-refinement'] --> B[Automation Triggered]; 15 | B --> C[Analyze Issue Description]; 16 | C --> D[Search Codebase for Related Files]; 17 | D --> E[Read Identified Files]; 18 | E --> F[Enhance Issue with Context and Criteria]; 19 | ``` 20 | 21 | ## How to Use 22 | 23 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 24 | 2. Label an issue with `needs-refinement`. 25 | 3. The automation will refine the issue by adding relevant context and acceptance criteria. 26 | 27 | ## Customization Ideas 28 | 29 | - Customize the `agent-instructions` within the workflow to tailor the refinement process based on the specific needs of your project. 30 | - Adjust the trigger conditions to include more types of interactions or to narrow down the scope to very specific types of issues. 31 | 32 | This automation provides a structured approach to issue refinement, helping to clarify the issue's scope and requirements before further action is taken. 33 | -------------------------------------------------------------------------------- /automations/refine-issue/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🔍 Refine Issue" 2 | 3 | # Triggers the workflow when a `needs-refinement` label is added to an issue 4 | on: 5 | issues: 6 | types: [labeled] 7 | 8 | jobs: 9 | refine-issue: 10 | runs-on: ubuntu-latest 11 | if: "github.event.label.name == 'needs-refinement'" 12 | steps: 13 | - name: Refine Issue Content 14 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 15 | with: 16 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 17 | agent-instructions: | 18 | We have a Github issue that needs to be worked on, but requires more context information first. 19 | 20 | 1. Read the issue with ID `${{ github.event.issue.number }}`. 21 | 2. Analyze the issue description to identify keywords. 22 | 3. Search the codebase for files related to these keywords. 23 | 4. Read the identified files. 24 | 5. Based on the issue content and the contents of the files you read, change the issue: 25 | 26 | - Issue body should have `Technical Details` part with bullet points that will make it easier to implement the issue 27 | - Issue body should have `Acceptance Criteria` part with concise, verifyable acceptance criteria 28 | - Acceptance criteria must be Markdown checkboxes 29 | - Acceptance criteria must be verifyable exclusively by reading files (no running scripts, tests, etc) 30 | - Issue title should start with an emoji 31 | - Remove the `needs-refinement` label 32 | -------------------------------------------------------------------------------- /automations/work-on-todo-list/README.md: -------------------------------------------------------------------------------- 1 | # 📋 Work on TODO List Automation 2 | 3 | **ID**: `work-on-todo-list` 4 | 5 | This automation is designed to automatically work on items listed in the `TODO.md` file on the main branch. When `TODO.md` is updated, the automation identifies the next open item on the list and fulfills it to the best of its abilities. If all items are completed, it deletes the `TODO.md` file. 6 | 7 | ## How it Works 8 | 9 | - **Trigger Conditions:** The workflow is triggered when `TODO.md` on the main branch is changed. 10 | - **Action Process:** The automation reads `TODO.md`, identifies the next open item, and works on fulfilling that task. If all tasks are completed, `TODO.md` is deleted. 11 | 12 | ```mermaid 13 | graph TD; 14 | A[TODO.md Updated] --> B[Automation Triggered]; 15 | B --> C[Identify Next Open Item]; 16 | C --> D[Work on Item]; 17 | D --> E[All Items Done?]; 18 | E -->|Yes| F[Delete TODO.md]; 19 | E -->|No| C; 20 | ``` 21 | 22 | ## How to Use 23 | 24 | 1. Ensure the **[Workflow YAML](./workflow.yaml)** file is placed in your `.github/workflows` directory. 25 | 2. Update `TODO.md` on the main branch as needed. 26 | 3. The automation will automatically work on the next open item in the TODO list or delete the file if all items are completed. 27 | 28 | ## Customization Ideas 29 | 30 | - Customize the `agent-instructions` within the workflow to tailor the task fulfillment process based on the specific needs of your project or the nature of the tasks listed in `TODO.md`. 31 | -------------------------------------------------------------------------------- /automations/work-on-todo-list/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "📋 Work on TODO List" 2 | 3 | on: 4 | push: 5 | paths: 6 | - 'TODO.md' 7 | branches: 8 | - main 9 | 10 | jobs: 11 | work-on-todo-list: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Work on Next TODO Item 15 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 16 | with: 17 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 18 | agent-instructions: | 19 | 1. Read `TODO.md` 20 | 2. Identify the next open item on the TODO list. 21 | 3. Fulfill the identified task to the best of your abilities. 22 | 4. Edit `TODO.md` to mark the item you worked on as checked 23 | 5. If all items on the TODO list are completed, delete `TODO.md` 24 | -------------------------------------------------------------------------------- /index.yaml: -------------------------------------------------------------------------------- 1 | tools: 2 | answer-question: 3 | name: "🤖 Answer Question" 4 | description: "Ask a question and the bot will find the answer for you." 5 | labels: [question, answer] 6 | quick-task: 7 | name: "🚀 Quick Task" 8 | description: "Ask the bot to perform a task for you using its capabilities." 9 | labels: [] 10 | generate-automation: 11 | name: "🧙‍♂️ Generate Automation" 12 | description: "Generates a new Automation tailored to your project's needs." 13 | labels: [generate, automation, meta] 14 | generate-tool: 15 | name: "🧙‍♂️ Generate Tool" 16 | description: "Generates a new Tool tailored to your project's needs." 17 | labels: [generate, tool, meta] 18 | import-workflow: 19 | name: "🔄 Import Workflow" 20 | description: "Install a Smart Workflow into your project with the click of a button." 21 | labels: [import, workflow, meta] 22 | quick-code-change: 23 | name: "🛠 Quick Code Change" 24 | description: "Facilitate quick code modifications through an AI agent based on user inputs." 25 | labels: [code, modify, ai] 26 | write-user-story: 27 | name: "✍️ Write User Story" 28 | description: "Generate comprehensive user stories for your code base." 29 | labels: [user-story, best-practices, product] 30 | write-technical-specification: 31 | name: "✍️ Write Technical Specification" 32 | description: "Generates technical specifications based on user stories through an AI agent." 33 | labels: [specification, user-story, ai] 34 | draw-diagram: 35 | name: "📊 Draw Diagram" 36 | description: "Fenerate Mermaid diagrams based on the repository's code and files." 37 | labels: [diagram, visualize] 38 | initialize-project: 39 | name: "🚀 Initialize Project" 40 | description: "Assist users in setting up a new project by generating a Github issue with concise, actionable instructions and a list of files to be created, based on the specified programming language and optional framework." 41 | labels: [initialize, project, setup] 42 | automations: 43 | format-issue: 44 | name: "📝 Format and Label New Issues" 45 | description: "Automatically format and label new issues." 46 | labels: [issues, format, label] 47 | chat-bot: 48 | name: "🤖 Chat Bot" 49 | description: "Turn any issue into a chat with the bot by adding the `chat` label." 50 | labels: [chat, label, comment, issues] 51 | pr-auto-review: 52 | name: "🔍 PR Auto Review" 53 | description: "Automatically review new pull requests." 54 | labels: [review, pr, code-quality] 55 | investigate-bug: 56 | name: "🐞 Investigate Bug" 57 | description: "Automatically investigates issues labeled as `bug` by analyzing the codebase and providing suggestions." 58 | labels: [bug, investigate, code-analysis] 59 | help-with-documentation: 60 | name: "📚 Help with Documentation" 61 | description: "Automatically assists with documentation tasks when the `needs-documentation` label is added to an issue." 62 | labels: [documentation, help, automate] 63 | refine-issue: 64 | name: "🔍 Refine Issue" 65 | description: "Automatically refines issues labeled with `needs-refinement` by analyzing the issue description, searching the codebase for related files, and enhancing the issue with relevant context and acceptance criteria." 66 | labels: [refinement, context, criteria] 67 | help-with-implementation: 68 | name: "🛠 Help with Implementation" 69 | description: "Automatically assists with implementation tasks when the `needs-work` label is added to an issue by reading the issue, understanding the requirements, searching for related files, and writing the necessary changes." 70 | labels: [implementation, code-change, automate] 71 | enforce-contribution-guidelines: 72 | name: "📐 Enforce Contribution Guidelines" 73 | description: "Automatically ensures that new pull requests adhere to the project's contribution guidelines." 74 | labels: [contribution, guidelines, pr] 75 | work-on-todo-list: 76 | name: "📋 Work on TODO List" 77 | description: "Automatically works on items listed in the TODO.md file when updated on the main branch. If all items are completed, it deletes the TODO.md file." 78 | labels: [todo, automate, task] 79 | product-owner: 80 | name: "👩‍💼 Product Owner" 81 | description: "Acts as a virtual Product Owner, modifying issues labeled with `feature-request` to include structured sections for user story, functional and non-functional requirements, and out of scope." 82 | labels: [feature-request, user-story, requirements] -------------------------------------------------------------------------------- /tools/answer-question/README.md: -------------------------------------------------------------------------------- 1 | # 🤖 Answer Question 2 | 3 | **ID**: `answer-question` 4 | 5 | A tool designed to answer questions by searching the codebase and, if necessary, the internet for relevant information. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Click the `Actions` tab in your repository and select the `🤖 Answer Question` workflow. 11 | 3. When prompted, enter your question in the input field provided. 12 | 13 | ## Inputs 14 | 15 | This tool requires the following input: 16 | 17 | | Input | Description | Example | 18 | | --- | --- | --- | 19 | | `question` | The question you want answered. | `How does the quick-task tool work?` | 20 | -------------------------------------------------------------------------------- /tools/answer-question/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🤖 Answer Question" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | question: 7 | description: 'What is your question?' 8 | required: true 9 | 10 | jobs: 11 | answer-question: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Respond to Question 15 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 16 | with: 17 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 18 | agent-instructions: | 19 | The user has a question: 20 | 21 | ``` 22 | ${{ github.event.inputs.question }} 23 | ``` 24 | 25 | 1. Understand the question. 26 | 2. Search the code base using ripgrep for any relevant information. 27 | 3. If necessary, search the internet for information. 28 | 4. Answer the question based on the information found in the code base and/or internet. 29 | -------------------------------------------------------------------------------- /tools/draw-diagram/README.md: -------------------------------------------------------------------------------- 1 | # 📊 Draw Diagram 2 | 3 | **ID**: `draw-diagram` 4 | 5 | A tool designed to quickly let you generate [Mermaid diagrams](https://mermaid.js.org/). 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Navigate to the `Actions` tab in your repository and select the `📊 Draw Diagram` workflow. 11 | 3. Provide the `diagram-type` and `what-to-visualize` inputs as per your requirements. 12 | 13 | ## Inputs 14 | 15 | This tool requires the following inputs: 16 | 17 | | Input | Description | Example | 18 | |-------------------|--------------------------------------------------|------------------------------------------| 19 | | `diagram-type` | The type of Mermaid diagram you want to create. | flow diagram | 20 | | `what-to-visualize` | Describe what aspect of the project to visualize. | Interaction between `TaskEngine` and `TaskScheduler` classes | 21 | -------------------------------------------------------------------------------- /tools/draw-diagram/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "📊 Draw Diagram" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | diagram-type: 7 | description: 'Specify the type of diagram to create.' 8 | required: true 9 | what-to-visualize: 10 | description: 'Describe what to visualize in the diagram.' 11 | required: true 12 | 13 | jobs: 14 | generate_diagram: 15 | runs-on: ubuntu-latest 16 | steps: 17 | - name: Generate Diagram 18 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 19 | with: 20 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 21 | agent-instructions: | 22 | I want a Mermaid diagram for the following: 23 | ${{ inputs.what-to-visualize }} 24 | 25 | It should be a diagram of type: 26 | ${{ inputs.diagram-type }} 27 | 28 | 1. Search the repository to find code and read files relevant to what we want to visualize 29 | 2. Create a new issue titled " Diagram of ". 30 | 3. In the issue body, put the Mermaid diagram and a description 31 | -------------------------------------------------------------------------------- /tools/generate-automation/README.md: -------------------------------------------------------------------------------- 1 | # 🧙‍♂️ Generate Automation 2 | 3 | **ID**: `generate-automation` 4 | 5 | A powerful tool that enables the creation of custom automations within your GitHub repository. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Navigate to the `Actions` tab in your repository and select the `🧙‍♂️ Generate Automation` workflow. 11 | 3. Fill in the required inputs: 12 | - **Automation Name**: The name you want to give to your automation. 13 | - **Trigger**: What event should trigger the automation? 14 | - **Agent Instructions**: Detailed instructions for what the agent should do when the automation is triggered. 15 | 16 | ## Inputs 17 | 18 | This tool requires the following inputs: 19 | 20 | | Input | Description | Example | 21 | | --- | --- | --- | 22 | | `automation-name` | The name of the automation you're creating. | `Auto Label Issues` | 23 | | `trigger` | The GitHub event that triggers the automation. | `When a new issue is opened` | 24 | | `agent-instructions` | Detailed instructions for the agent to follow when the automation is triggered. | `Add labels based on the issue content` | 25 | -------------------------------------------------------------------------------- /tools/generate-automation/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🧙‍♂️ Generate Automation" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | automation-name: 7 | description: 'Name of the automation' 8 | required: true 9 | trigger: 10 | description: 'What should trigger the automation?' 11 | required: true 12 | agent-instructions: 13 | description: 'What should the agent do when the automation is triggered?' 14 | required: true 15 | 16 | jobs: 17 | create-new-automation: 18 | runs-on: ubuntu-latest 19 | steps: 20 | - name: Create New Automation 21 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 22 | with: 23 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 24 | agent-instructions: | 25 | Your task is to generate a new Github workflow. 26 | The workflow's purpose is to have an AI agent respond to a given trigger in the repository. 27 | 28 | The workflow should be called `${{ github.event.inputs.automation-name }}`. 29 | 30 | It should be triggered when: 31 | ``` 32 | ${{ github.event.inputs.trigger }} 33 | ``` 34 | 35 | When triggered, the user wants the agent to do the following: 36 | ``` 37 | ${{ github.event.inputs.agent-instructions }} 38 | ``` 39 | 40 | These instructions need to be turned into an actionable step-by-step guide for the AI agent to follow. 41 | Make sure the step-by-step instructions are clear and concise. 42 | 43 | Assume that the agent has the same capabilities as you do. It is important to only include 44 | instructions that are within the agent's capabilities. 45 | 46 | The workflow file must fulfill the following criteria: 47 | - Name of the workflow starts with an emoji (UTF-8 character) 48 | - Has only one job with one step that uses `PR-Pilot-AI/smart-actions/quick-task@v1` 49 | - The step should have the following inputs: 50 | - `api-key` (similar to reference workflow) 51 | - `agent-instructions` (Step-by-step instructions for the AI agent) 52 | 53 | If the agent's task requires data from the workflow run (e.g. issue ID, commit msg, etc), 54 | then the text for `agent-instructions` should have these values injected into them using the 55 | github context variables. 56 | 57 | Do the following: 58 | 1. Read `automations/format-issue/workflow.yaml` as reference to understand the desired structure of the workflow file. 59 | 2. Turn the free-text instructions provided by the user into actionable step-by-step instructions for the AI agent. 60 | 3. Generate the new Github workflow file in `automations//workflow.yaml` 61 | 4. Read `automations/format-issue/README.md` as reference to understand the desired structure of the README file for the workflow. 62 | 5. Generate the new README file in `automations//README.md` 63 | 6. Add the automation to `index.yaml` with the appropriate details 64 | 7. Add the automation to the README.md file with the appropriate details 65 | -------------------------------------------------------------------------------- /tools/generate-tool/README.md: -------------------------------------------------------------------------------- 1 | # 🧙‍♂️ Generate Tool 2 | 3 | **ID**: `generate-tool` 4 | 5 | A powerful tool that automates the creation of custom tools for your Github project. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Click the `Actions` tab in your repository and select the `🧙‍♂️ Generate Tool` workflow. 11 | 12 | ## Inputs 13 | 14 | This tool requires the following inputs: 15 | 16 | | Input | Description | Example | 17 | | --- |-------------------------------------------------------------------------------|--------------------------------------------------------| 18 | | `tool-name` | Name of the tool you want to create. | `Issue Summarizer` | 19 | | `tool-inputs` | Inputs required for the tool. | `The issue number` | 20 | | `agent-instructions` | Detailed instructions for what the agent should do when the tool is executed. | `Summarize the issue and add the summary as a comment` | 21 | | `template-tool` | ID of the tool to use as a base for the new tool. | `quick-code-change` | 22 | -------------------------------------------------------------------------------- /tools/generate-tool/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🧙‍♂️ Generate Tool" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | tool-name: 7 | description: 'Name of the tool' 8 | required: true 9 | tool-inputs: 10 | description: 'Inputs required for the tool' 11 | required: true 12 | agent-instructions: 13 | description: 'What should the agent do when the tool is executed?' 14 | required: true 15 | template-tool: 16 | description: 'ID of the tool to be used as example' 17 | required: true 18 | default: 'quick-code-change' 19 | 20 | jobs: 21 | automate-tool-creation: 22 | runs-on: ubuntu-latest 23 | steps: 24 | - name: Automate Tool Creation 25 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 26 | with: 27 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 28 | agent-instructions: | 29 | Your task is to generate a new Github workflow. 30 | The workflow's purpose is to serve as a tool for the user to interact with an AI agent 31 | that can operate on the repository. 32 | 33 | The workflow should be called `${{ github.event.inputs.tool-name }}`. 34 | 35 | It should have the following inputs: 36 | ``` 37 | ${{ github.event.inputs.tool-inputs }} 38 | ``` 39 | 40 | When triggered, the user wants the agent to do the following with the given inputs: 41 | ``` 42 | ${{ github.event.inputs.agent-instructions }} 43 | ``` 44 | 45 | These instructions need to be turned into an actionable step-by-step guide for the AI agent to follow. 46 | Make sure the step-by-step instructions are clear and concise. 47 | 48 | Assume that the agent has the same capabilities as you do. It is important to only include 49 | instructions that are within the agent's capabilities. 50 | 51 | The workflow file must fulfill the following criteria: 52 | - Name of the workflow starts with an emoji (UTF-8 character) 53 | - Has only one job with one step that uses `PR-Pilot-AI/smart-actions/quick-task@v1` 54 | - The step should have the following inputs: 55 | - `api-key` (similar to reference workflow) 56 | - `agent-instructions` (Step-by-step instructions for the AI agent) 57 | 58 | If the agent's task requires data from the workflow run (e.g. issue ID, commit msg, etc), 59 | then the text for `agent-instructions` should have these values injected into them using the 60 | github context variables. 61 | 62 | Do the following: 63 | 1. Read `tools/${{ github.event.inputs.template-tool }}/workflow.yaml` as reference to understand the desired structure of the workflow file. 64 | 2. Turn the free-text instructions provided by the user into actionable step-by-step instructions for the AI agent. 65 | 3. Generate the new Github workflow file in `tools//workflow.yaml` 66 | 4. Read `tools/${{ github.event.inputs.template-tool }}/README.md` as reference to understand the desired structure of the README file for the workflow. 67 | 5. Generate the new README file in `tools//README.md` 68 | 6. Add the tool to `index.yaml` with the appropriate details 69 | 7. Add the tool to the README.md file with the appropriate details -------------------------------------------------------------------------------- /tools/import-workflow/README.md: -------------------------------------------------------------------------------- 1 | # 🔄 Import Workflow 2 | 3 | **ID**: `import-workflow` 4 | 5 | Enables you to install a Smart Workflow into your project with the click of a button. 6 | 7 | ## How to Install 8 | 9 | 1. **[Install the AI agent](https://github.com/apps/pr-pilot-ai/installations/new)** on your repository 10 | 2. Copy **[workflow.yaml](./workflow.yaml)** into your `.github/workflows` directory 11 | 12 | ## How to Use 13 | 14 | 1. Navigate to the `Actions` tab in your repository. 15 | 2. Select the `🔄 Import Workflow` from the list of workflows. 16 | 3. Provide the ID of the workflow you wish to import in the input field. 17 | 4. The AI agent will then attempt to find and import the specified workflow into your `.github/workflows` directory. 18 | 19 | The tool will create a PR with your new workflow and suggestions for how to customize it 20 | to better fit your project's needs. 21 | 22 | ## Inputs 23 | 24 | This tool requires the following input: 25 | 26 | | Input | Description | Example | 27 | |---------------|--------------------------------------------|------------| 28 | | `workflow-id` | The ID of the workflow you want to import. | `chat-bot` | 29 | -------------------------------------------------------------------------------- /tools/import-workflow/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: 🔄 Import Smart Workflow 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | workflow-id: 7 | description: ID of the workflow to import 8 | required: true 9 | 10 | jobs: 11 | setup: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Checkout PR-Pilot-AI/smart-workflows 15 | uses: actions/checkout@v2 16 | with: 17 | repository: PR-Pilot-AI/smart-workflows 18 | token: ${{ secrets.GITHUB_TOKEN }} 19 | - name: Determine workflow file path 20 | id: filepath 21 | run: | 22 | if [ -f tools/${{ github.event.inputs.workflow-id }}/workflow.yaml ]; then 23 | echo "::set-output name=path::tools/${{ github.event.inputs.workflow-id }}/workflow.yaml" 24 | elif [ -f automations/${{ github.event.inputs.workflow-id }}/workflow.yaml ]; then 25 | echo "::set-output name=path::automations/${{ github.event.inputs.workflow-id }}/workflow.yaml" 26 | else 27 | echo "Path not found" && exit 1 28 | fi 29 | - name: Copy workflow file 30 | id: print-workflow 31 | run: | 32 | workflow=$(cat ${{ steps.filepath.outputs.path }}) 33 | echo "WORKFLOW<> "$GITHUB_OUTPUT" 34 | 35 | - name: Import Workflow 36 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 37 | with: 38 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 39 | agent-instructions: | 40 | Create a new file in `.github/workflows/` for the following workflow: 41 | 42 | --- 43 | 44 | ${{ steps.print-workflow.outputs.WORKFLOW }} 45 | 46 | --- 47 | 48 | Respond to the user with a few suggestions on how they could customize the workflow for this project. 49 | -------------------------------------------------------------------------------- /tools/initialize-project/README.md: -------------------------------------------------------------------------------- 1 | # 🚀 Initialize Project 2 | 3 | **ID**: `initialize-project` 4 | 5 | A tool designed to assist users in setting up a new project by generating a Github issue with concise, actionable instructions and a list of files to be created, based on the specified programming language and optional framework. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Navigate to the `Actions` tab in your repository and select the `🚀 Initialize Project` workflow. 11 | 3. Provide the `programming-language`, `framework` (optional), and `project-description` inputs as per your requirements. 12 | 13 | ## Inputs 14 | 15 | This tool requires the following inputs: 16 | 17 | | Input | Description | Example | 18 | |----------------------|-----------------------------------------------|------------------| 19 | | `programming-language` | The programming language of the project. | `Python` | 20 | | `framework` | The framework to be used (optional). | `Django` | 21 | | `project-description` | A brief description of the project. | `A web application for managing tasks.` | 22 | -------------------------------------------------------------------------------- /tools/initialize-project/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🚀 Initialize Project" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | programming-language: 7 | description: 'The programming language of the project.' 8 | required: true 9 | framework: 10 | description: 'The framework to be used (optional).' 11 | required: false 12 | project-description: 13 | description: 'A brief description of the project.' 14 | required: true 15 | 16 | jobs: 17 | setup_project: 18 | runs-on: ubuntu-latest 19 | steps: 20 | - name: Setup Project Instructions 21 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 22 | with: 23 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 24 | agent-instructions: | 25 | This is an empty project and we want to initialize it. 26 | 27 | Programming language: ${{ github.event.inputs.programming-language }} 28 | Framework (optional): ${{ github.event.inputs.framework }} 29 | Project description: 30 | ${{ github.event.inputs.project-description }} 31 | 32 | 1. Use the programming language and framework (if provided) to search the internet for information on how to start a project with these specifications. 33 | 2. Compile the information into concise, actionable instructions for starting the project, including a list of initial files that need to be created. 34 | 3. Create a Github issue in the repository with the compiled instructions and detailed list of files to create. Label the issue `needs-refinement`. 35 | -------------------------------------------------------------------------------- /tools/quick-code-change/README.md: -------------------------------------------------------------------------------- 1 | # 🛠 Quick Code Change 2 | 3 | **ID**: `quick-code-change` 4 | 5 | A tool designed to facilitate quick code modifications through an AI agent, based on user inputs. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Navigate to the `Actions` tab in your repository and select the `🛠 Quick Code Change` workflow. 11 | 3. Provide the `code-to-change` and `how-to-change-it` inputs as per your requirements. 12 | 13 | ## Inputs 14 | 15 | This tool requires the following inputs: 16 | 17 | | Input | Description | Example | 18 | |------------------|---------------------------------------|------------------------------------------| 19 | | `code-to-change` | The code or file you want to modify. | `src/components/Button.js` | 20 | | `how-to-change-it` | Instructions on how to modify the code. | `Change the button color to blue.` | -------------------------------------------------------------------------------- /tools/quick-code-change/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🛠 Quick Code Change" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | code-to-change: 7 | description: 'Specify the code or file to change.' 8 | required: true 9 | how-to-change-it: 10 | description: 'Describe how to change the code.' 11 | required: true 12 | 13 | jobs: 14 | execute_code_change: 15 | runs-on: ubuntu-latest 16 | steps: 17 | - name: Execute Code Change 18 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 19 | with: 20 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 21 | agent-instructions: | 22 | Read the following code: 23 | ${{ inputs.code-to-change }} 24 | 25 | and change it in the following way: 26 | ${{ inputs.how-to-change-it }} 27 | -------------------------------------------------------------------------------- /tools/quick-task/README.md: -------------------------------------------------------------------------------- 1 | # 🚀 Quick Task 2 | 3 | **ID**: `quick-task` 4 | 5 | A simple tool that lets quickly lets you hand off work to the AI agent. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Click the `Actions` tab in your repository and select the `🚀 Quick Task` workflow. 11 | 12 | ## Inputs 13 | 14 | This tool requires the following inputs: 15 | 16 | | Input | Description | Example | 17 | | --- | --- |------------------------------------------------------------------------| 18 | | `task` | The task you want the AI agent to perform. | `Summarize the README file and create a Github issue with the result.` | -------------------------------------------------------------------------------- /tools/quick-task/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "🚀 Quick Task" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | agent-instructions: 7 | description: 'What should the agent do for you?' 8 | required: true 9 | 10 | jobs: 11 | execute_quick_task: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Execute AI Task 15 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 16 | with: 17 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 18 | agent-instructions: ${{ github.event.inputs.agent-instructions }} 19 | -------------------------------------------------------------------------------- /tools/write-technical-specification/README.md: -------------------------------------------------------------------------------- 1 | # ✍️ Write Technical Specification 2 | 3 | **ID**: `write-technical-specification` 4 | 5 | A workflow designed to help users interact with an AI agent to generate technical specifications based on user stories. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Click the `Actions` tab in your repository and select the `✍️ Write Technical Specification` workflow. 11 | 3. Provide the `user-story` input with either the issue number or a text description of the user story. 12 | 13 | ## Inputs 14 | 15 | This tool requires the following input: 16 | 17 | | Input | Description | Example | 18 | | --- | --- | --- | 19 | | `user-story` | The issue number or text description of the user story. | `42` or `As a user, I want to be able to upload files directly from the UI.` | -------------------------------------------------------------------------------- /tools/write-technical-specification/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "✍️ Write Technical Specification" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | user-story: 7 | description: 'Issue number or text description of the user story' 8 | required: true 9 | 10 | jobs: 11 | generate_specification: 12 | runs-on: ubuntu-latest 13 | steps: 14 | - name: Generate Technical Specification 15 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 16 | with: 17 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 18 | agent-instructions: | 19 | We have a user story (either issue number or text description): 20 | ${{ inputs.user-story }} 21 | 22 | 1. Read the user story from the input. If it's an issue number, use `functions.read_github_issue` to get the details. If it's a text description, proceed with that. 23 | 2. Based on the user story, identify keywords or phrases that describe the feature or bug fix. 24 | 3. Use `functions.search_with_ripgrep` to find relevant files in the codebase that might be related to the user story. 25 | 4. Read the identified files. 26 | 5. Synthesize the information from the user story and the code to draft a technical specification. 27 | 6. Open a new issue with the title 'Technical Specification for [User Story Title]' and tag it `specification`. The body should contain a structured description of the necessary code changes to implement the story. 28 | -------------------------------------------------------------------------------- /tools/write-user-story/README.md: -------------------------------------------------------------------------------- 1 | # ✍️ Write User Story 2 | 3 | **ID**: `write-user-story` 4 | 5 | A workflow designed to facilitate the creation of comprehensive user stories by interacting with an AI agent. This tool allows users to input a user story and relevant context, which the AI then uses to generate a detailed issue encompassing the story, scope, value, and acceptance criteria. 6 | 7 | ## How to Use 8 | 9 | 1. Copy the **[Workflow YAML](./workflow.yaml)** file into your `.github/workflows` directory. 10 | 2. Click the `Actions` tab in your repository and select the `✍️ Write User Story` workflow. 11 | 3. Provide the `user-story` and `relevant-context` inputs as required. 12 | 13 | ## Inputs 14 | 15 | This tool requires the following inputs: 16 | 17 | | Input | Description | Example | 18 | | --- | --- | --- | 19 | | `user-story` | The user story in the format: As ..., I want to ..., so ... | `As a developer, I want to generate user stories, so I can better track my project's progress.` | 20 | | `relevant-context` | Any relevant code, keywords, etc, that will help the AI understand the context of the user story. | `Github Actions, AI integration` | -------------------------------------------------------------------------------- /tools/write-user-story/workflow.yaml: -------------------------------------------------------------------------------- 1 | name: "✍️ Write User Story" 2 | 3 | on: 4 | workflow_dispatch: 5 | inputs: 6 | user-story: 7 | description: 'As ... I want to... so...' 8 | required: true 9 | relevant-context: 10 | description: 'Code, keywords, etc' 11 | required: true 12 | 13 | jobs: 14 | generate_user_story: 15 | runs-on: ubuntu-latest 16 | steps: 17 | - name: Generate User Story Issue 18 | uses: PR-Pilot-AI/smart-actions/quick-task@v1 19 | with: 20 | api-key: ${{ secrets.PR_PILOT_API_KEY }} 21 | agent-instructions: | 22 | I have the following user story: 23 | ${{ inputs.user-story }} 24 | 25 | Relevant context: 26 | ${{ inputs.relevant-context }} 27 | 28 | I want a comprehensive user story with: 29 | - The story itself 30 | - Markdown links to the relevant context files or websites 31 | - Clearly defined scope 32 | - Value of the story to the user 33 | - List of checkbox acceptance criteria 34 | 35 | 1. Search the code or internet for relevant context and read it 36 | 2. Open a new issue containing the full, comprehensive user story and label it `user-story` 37 | --------------------------------------------------------------------------------