simplify includes

dsyme · dsyme · commit 691046d9de0b · 2025-10-02T20:07:39.000+01:00
diff --git a/docs/ci-doctor.md b/docs/ci-doctor.md
@@ -18,11 +18,7 @@ This creates a pull request to add the workflow to your repository. After mergin
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. Use local configuation to specify which workflows to monitor (currently monitors "Daily Perf Improver" and "Daily Test Improver"), investigation depth, failure categorization, and reporting format. Local configuration can be done in `.github/workflows/agentics/ci-doctor.config.md`.
-
-2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`. 
+You can specify which workflows to monitor (currently monitors "Daily Perf Improver" and "Daily Test Improver") by editing the workflow directly.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-accessibility-review.md b/docs/daily-accessibility-review.md
@@ -24,11 +24,7 @@ gh aw run daily-accessibility-review
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. Use local configuation to specify which accessibility standards to check (e.g., WCAG 2.1, WCAG 2.2), types of accessibility issues to prioritize, and reporting format. Local configuration can be done in `.github/workflows/agentics/daily-accessibility-review.config.md`.
-
-2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`. 
+This workflow requires no configuration and works out of the box. You can use local configuation to specify which accessibility standards to check (e.g., WCAG 2.1, WCAG 2.2), types of accessibility issues to prioritize, and reporting format. Local configuration can be done in `.github/workflows/agentics/daily-accessibility-review.config.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-dependency-updates.md b/docs/daily-dependency-updates.md
@@ -38,11 +38,9 @@ gh aw run daily-dependency-updates
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+This workflow requires no configuration and works out of the box. You can use local configuation to specify dependency management tools (npm, pip, maven, etc.), customize dependency update strategies and version constraints, onfigure which dependencies to include/exclude from automated updates. Local configuration can be done in `.github/workflows/agentics/daily-dependency-updates.config.md`.
 
-1. Use local configuation to specify dependency management tools (npm, pip, maven, etc.), customize dependency update strategies and version constraints, onfigure which dependencies to include/exclude from automated updates. Local configuration can be done in `.github/workflows/agentics/daily-dependency-updates.config.md`.
 
-2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-perf-improver.md b/docs/daily-perf-improver.md
@@ -52,8 +52,6 @@ gh aw run daily-perf-improver --repeat 180
 
 3. Use local configuation to specify performance testing tools and benchmarking frameworks, optimization targets, performance metrics, and profiling strategies. Local configuration can be done in `.github/workflows/agentics/daily-perf-improver.config.md`.
 
-4. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`. 
-
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## What it reads from GitHub
diff --git a/docs/daily-plan.md b/docs/daily-plan.md
@@ -22,9 +22,7 @@ gh aw run daily-plan
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. Use local configuation to specify planning focus areas, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
+This workflow requires no configuration and works out of the box. You can use local configuation to specify planning focus areas, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-progress.md b/docs/daily-progress.md
@@ -40,8 +40,6 @@ This workflow requires no configuration and works out of the box. However, you c
 
 2. **Build steps**: The workflow will automatically create a build configuration file at `.github/actions/daily-progress/build-steps/action.yml` to set up the development environment for feature work.
 
-3. **Build tools configuration**: Specify additional bash commands and tools in `.github/workflows/agentics/build-tools.md` (shared).
-
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## How it Works
diff --git a/docs/daily-qa.md b/docs/daily-qa.md
@@ -24,11 +24,9 @@ gh aw run daily-qa
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+This workflow requires no configuration and works out of the box. You can use local configuation to specify QA tasks, testing scenarios, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-qa.config.md`.
 
-1. Use local configuation to specify QA tasks, testing scenarios, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-qa.config.md`.
 
-2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/daily-team-status.md b/docs/daily-team-status.md
@@ -22,9 +22,7 @@ gh aw run daily-team-status
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. Use local configuation to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/daily-team-status.config.md`.
+This workflow requires no configuration and works out of the box. You can use local configuation to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/daily-team-status.config.md`.
 
 2. Add MCPs to integrate with project management tools
 
diff --git a/docs/daily-test-improver.md b/docs/daily-test-improver.md
@@ -46,8 +46,6 @@ gh aw run daily-test-improver
 
 3. Use local configuation or comment on the plan to specify test generation strategies, high-priority areas and coverage targets. Local configuration can be done in `.github/workflows/agentics/daily-test-improver.config.md`.
 
-4. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
-
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
 ## What it reads from GitHub
diff --git a/docs/issue-triage.md b/docs/issue-triage.md
@@ -18,9 +18,7 @@ This creates a pull request to add the workflow to your repository. You can't st
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. Use local configuation to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/issue-triage.config.md`.
+This workflow requires no configuration and works out of the box. You can use local configuation to customize triage criteria, labeling logic, customize issue categorization, modify automated responses. Local configuration can be done in `.github/workflows/agentics/issue-triage.config.md`.
 
 2. Add MCPs to integrate with project management tools
 
diff --git a/docs/pr-fix.md b/docs/pr-fix.md
@@ -54,11 +54,9 @@ IMPORTANT: GitHub Actions runs will **not** trigger on commits pushed by this wo
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+This workflow requires no configuration and works out of the box. You can use local configuration to specify custom build commands, testing procedures, linting rules, and code formatting standards. Local configuration can be done in `.github/workflows/agentics/pr-fix.config.md`.
 
-1. Use local configuration to specify custom build commands, testing procedures, linting rules, and code formatting standards. Local configuration can be done in `.github/workflows/agentics/pr-fix.config.md`.
-
-2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`. 
+ 
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/repo-ask.md b/docs/repo-ask.md
@@ -42,11 +42,7 @@ To trigger the workflow on a specific issue or pull request, add a comment with
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. **Local configuration**: Customize research behavior, response format, and allowed tools. Local configuration can be done in `.github/workflows/agentics/repo-ask.config.md`.
-
-2. **Build tools configuration**: Specify additional bash commands and tools in `.github/workflows/agentics/build-tools.md` (shared).
+This workflow requires no configuration and works out of the box. You can customize research behavior, response format, and allowed tools. Local configuration can be done in `.github/workflows/agentics/repo-ask.config.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/update-docs.md b/docs/update-docs.md
@@ -38,11 +38,9 @@ gh aw run update-docs
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
+This workflow requires no configuration and works out of the box. You can use local configuation to configure documentation frameworks, documentation structure, themes, files, directories. Local configuration can be done in `.github/workflows/agentics/update-docs.config.md`.
 
-1. Use local configuation to configure documentation frameworks, documentation structure, themes, files, directories. Local configuration can be done in `.github/workflows/agentics/update-docs.config.md`.
 
-2. Build tool configuration for build tools shared across all workflows installed from this pack can be done in `.github/workflows/agentics/build-tools.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/docs/weekly-research.md b/docs/weekly-research.md
@@ -22,9 +22,7 @@ gh aw run weekly-research
 
 ## Configuration
 
-This workflow requires no configuration and works out of the box. However, you can customize it as follows:
-
-1. Use local configuation to customize output format, research topics, report length, focus areas or to adjust frequency or timing. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
+This workflow requires no configuration and works out of the box. You can use local configuation to customize output format, research topics, report length, focus areas or to adjust frequency or timing. Local configuration can be done in `.github/workflows/agentics/daily-plan.config.md`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 
diff --git a/workflows/daily-backlog-burner.md b/workflows/daily-backlog-burner.md
@@ -23,13 +23,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/daily-progress.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
diff --git a/workflows/daily-progress.md b/workflows/daily-progress.md
@@ -23,13 +23,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/daily-progress.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
diff --git a/workflows/daily-qa.md b/workflows/daily-qa.md
@@ -25,13 +25,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/daily-qa-improver.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
diff --git a/workflows/daily-test-improver.md b/workflows/daily-test-improver.md
@@ -27,13 +27,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/daily-test-improver.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
diff --git a/workflows/pr-fix.md b/workflows/pr-fix.md
@@ -19,13 +19,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/pr-fix.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
diff --git a/workflows/repo-ask.md b/workflows/repo-ask.md
@@ -16,13 +16,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/pr-fix.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
diff --git a/workflows/update-docs.md b/workflows/update-docs.md
@@ -16,13 +16,6 @@ safe-outputs:
 tools:
   web-fetch:
   web-search:
-  # Configure bash build commands in any of these places
-  # - this file
-  # - .github/workflows/agentics/update-docs.config.md 
-  # - .github/workflows/agentics/build-tools.md (shared).
-  #
-  # Run `gh aw compile` after editing to recompile the workflow.
-  #
   # By default this workflow allows all bash commands within the confine of Github Actions VM 
   bash: [ ":*" ]
 
