Merge branch 'main' of https://github.com/githubnext/agentics

Author: pelikhan

docs/daily-team-status.md

@@ -44,8 +44,9 @@ This workflow requires no configuration and works out of the box. You can use lo
 
 ## What it creates
 
-- Creates new status report issues
-- Updates existing status issues with new information
+- Creates new daily status report issues with the `[team-status]` prefix
+- Automatically closes older status report issues to prevent clutter
+- Labels new issues with `report` and `daily-status` tags
 - Requires `issues: write` permission
 
 ## Human in the loop

workflows/daily-perf-improver.md

@@ -122,7 +122,7 @@ To decide which phase to perform:
 
 3. Create `.github/actions/daily-perf-improver/build-steps/action.yml` with validated build steps. Each step must log output to `build-steps.log` in repo root. Cross-check against existing CI/devcontainer configs.
 
-4. Create 1-5 performance engineering guides in `.github/copilot/instructions/` covering relevant areas (e.g., frontend performance, backend optimization, build performance, infrastructure scaling). Each guide should document:
+4. Create 1-5 performance engineering guides in `.github/copilot/instructions/` covering relevant areas (e.g., frontend performance, backend optimization, build performance, infrastructure scaling). Each guide should be maximum 500 words and should succinctly document practical, non-obvious, repo-specific details regarding:
   - Performance measurement strategies and tooling
   - Common bottlenecks and optimization techniques
   - Success metrics and testing approaches

workflows/daily-team-status.md

@@ -2,7 +2,7 @@
 description: |
   This workflow created daily team status reporter creating upbeat activity summaries.
   Gathers recent repository activity (issues, PRs, discussions, releases, code changes)
-  and generates engaging GitHub discussions with productivity insights, community
+  and generates engaging GitHub issues with productivity insights, community
   highlights, and project recommendations. Uses a positive, encouraging tone with
   moderate emoji usage to boost team morale.
 
@@ -19,14 +19,15 @@ network: defaults
 tools:
   github:
 safe-outputs:
-  create-discussion:
+  create-issue:
     title-prefix: "[team-status] "
-    category: "announcements"
+    labels: [report, daily-status]
+    close-older-issues: true
 ---
 
 # Daily Team Status
 
-Create an upbeat daily status report for the team as a GitHub discussion.
+Create an upbeat daily status report for the team as a GitHub issue.
 
 ## What to include
 
@@ -44,4 +45,4 @@ Create an upbeat daily status report for the team as a GitHub discussion.
 ## Process
 
 1. Gather recent activity from the repository
-2. Create a new GitHub discussion with your findings and insights
+2. Create a new GitHub issue with your findings and insights

workflows/pr-fix.md

@@ -46,14 +46,14 @@ You are an AI assistant specialized in fixing pull requests with failing CI chec
 
 4. Formulate a plan to follow the instructions. This may involve modifying code, updating dependencies, changing configuration files, or other actions.
 
-5. Implement the changes needed to follow the instructions.
+4. Implement the changes needed to follow the instructions.
 
-6. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.
+5. Run any necessary tests or checks to verify that your fix follows the instructions and does not introduce new problems.
 
-7. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards fixing any new issues they identify.
+6. Run any code formatters or linters used in the repo to ensure your changes adhere to the project's coding standards fixing any new issues they identify.
 
-8. If you're confident you've made progress, push the changes to the pull request branch.
+7. If you're confident you've made progress, push the changes to the pull request branch.
 
-9. Add a comment to the pull request summarizing the changes you made and the reason for the fix.
+8. Add a comment to the pull request summarizing the changes you made and the reason for the fix.