Merge pull request #4 from githubnext/d2

clarify

Author: dsyme

README.md

@@ -1,4 +1,64 @@
-# agents
-Agents definitions for gh-aw
+# GitHub Agentic Workflows (Samples)
+
+More information about the format at https://github.com/githubnext/gh-aw
+
+To install:
+
+```bash 
+gh extension install githubnext/gh-aw
+gh aw install githubnext/gh-aw-samples
+```
+
+## Weekly Researcher
+
+```bash
+gh aw add agentic-researcher
+git commit -a -m "Add agentic-researcher workflow"
+```
+
+## Security and Dependency Updater
+
+```bash
+gh aw add agentic-dependency-updater
+git commit -a -m "Add agentic-dependency-updater workflow"
+```
+
+## QA Engineer
+
+```bash
+gh aw add agentic-qa
+git commit -a -m "Add agentic-qa workflow"
+```
+
+## Triage Assistant
+
+```bash
+gh aw add agentic-triage
+git commit -a -m "Add agentic-triage workflow"
+```
+
+## Planner
+
+```bash
+gh aw add agentic-planner
+git commit -a -m "Add agentic-planner workflow"
+```
+
+## Job Summary
+
+```bash
+gh aw install githubnext/gh-aw-samples
+gh aw add job-summary
+git commit -a -m "Add job-summary workflow"
+```
+
+## Coder
+
+```bash
+gh aw install githubnext/gh-aw-samples
+gh aw add agentic-coder
+git commit -a -m "Add agentic-coder workflow"
+```
+
+
 
-- More information about the format at https://github.com/githubnext/gh-aw

workflows/agentic-dependency-updater.md

@@ -27,6 +27,7 @@ tools:
         update_issue,
         add_issue_comment,
         create_pull_request,
+        update_pull_request,
         get_code_scanning_alert,
         list_code_scanning_alerts,
         get_dependabot_alert,
@@ -54,11 +55,18 @@ tools:
 
 Your name is "${{ github.workflow }}". Your job is to act as an agentic coder for the GitHub repository `${{ env.GITHUB_REPOSITORY }}`. You're really good at all kinds of tasks. You're excellent at everything.
 
-1. Check the dependabot alerts in the repository. If there are any, update the dependencies to the latest versions and create a pull request with the changes. Try to bundle as many dependency updates as possible into one PR. Test the changes to ensure they work correctly, if the tests don't pass then divide and conquer and create separate pull requests for each dependency update.
+1. Check the dependabot alerts in the repository. If there are any that aren't already covered by existing non-Dependabot pull requests, update the dependencies to the latest versions, by updating actual dependencies in dependency declaration files (package.json etc), not just lock files, and create a pull request with the changes. Try to bundle as many dependency updates as possible into one PR. Test the changes to ensure they work correctly, if the tests don't pass then divide and conquer and create separate pull requests for each dependency update. If the tests do pass close any Dependabot PRs that are already open for the same dependency updates with a note that the changes have been made in a different PR.
 
-2. Deal with any security alerts in the repository. If there are any, fix the security alerts, using one PR for each unless they are the same root cause issue. In each case test the changes to ensure they work correctly.
+   - Use the `list_dependabot_alerts` tool to retrieve the list of Dependabot alerts.
+   - Use the `get_dependabot_alert` tool to retrieve details of each alert.
+   - Use the `create_pull_request` tool to create a pull request with the changes.
+   - Use the `update_pull_request` tool to update pull requests with any additional changes.
 
-In both cases, you can use the `list_de_dependabot_alerts`, `get_dependabot_alert`, `list_code_scanning_alerts` and `get_code_scanning_alerts` tools to retrieve the alerts, and then use the `create_pull_request` tool to create a pull request with the changes.
+2. Deal with any security alerts in the repository. If there are any, fix the security alerts, using one PR for each unless they are the same root cause issue. First check if an existing PR exists for each security alert and if it does, skip it. In each case test the changes to ensure they work correctly.
+
+    - Use the `list_code_scanning_alerts` tool to retrieve the list of code scanning alerts.
+    - Use the `get_code_scanning_alert` tool to retrieve details of each alert.
+    - Use the `create_pull_request` tool to create a pull request with the changes.
 
 > NOTE: If you didn't make progress on a particular dependency update or security issue, add a comment saying what you've tried, ask for clarification if necessary, and add a link to a new branch containing any investigations you tried.