Add typos CI workflow and fix existing spelling errors

.github/workflows/ci.yml

@@ -1,4 +1,4 @@
-name: Install gh-aw
+name: Compile workflows with latest gh-aw release
 
 on:
   push:

.github/workflows/typos.yml

@@ -0,0 +1,21 @@
+name: Typos
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  typos:
+    name: Spell Check with Typos
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Check for typos
+        uses: crate-ci/[email protected]

docs/daily-accessibility-review.md

@@ -32,7 +32,7 @@ gh aw run daily-accessibility-review
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration 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.
 

docs/daily-dependency-updates.md

@@ -42,7 +42,7 @@ gh aw run daily-dependency-updates
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration to specify dependency management tools (npm, pip, maven, etc.), customize dependency update strategies and version constraints, configure which dependencies to include/exclude from automated updates. Local configuration can be done in `.github/workflows/agentics/daily-dependency-updates.config.md`.
 
 
 

docs/daily-perf-improver.md

@@ -58,7 +58,7 @@ gh aw run daily-perf-improver --repeat 180
 
 2. The first run of the workflow will also create an issue in the repository with a plan for improving performance. You can comment on this issue to provide feedback or adjustments to the plan. Comments will not be picked up until the next run.
 
-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`.
+3. Use local configuration 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`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 

docs/daily-plan.md

@@ -30,7 +30,7 @@ gh aw run daily-plan
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration 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.
 

docs/daily-qa.md

@@ -32,7 +32,7 @@ gh aw run daily-qa
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration to specify QA tasks, testing scenarios, reporting format, and frequency. Local configuration can be done in `.github/workflows/agentics/daily-qa.config.md`.
 
 
 

docs/daily-team-status.md

@@ -30,7 +30,7 @@ gh aw run daily-team-status
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration 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
 

docs/daily-test-improver.md

@@ -52,7 +52,7 @@ gh aw run daily-test-improver
 
 2. The first run of the workflow will also create an issue in the repository with a plan for improving test coverage. You can comment on this issue to provide feedback or adjustments to the plan. Comments will not be picked up until the next run.
 
-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`.
+3. Use local configuration 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`.
 
 After editing run `gh aw compile` to update the workflow and commit all changes to the default branch.
 

docs/issue-triage.md

@@ -26,7 +26,7 @@ You can't start a run of this workflow directly as it is triggered in the contex
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration 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
 

docs/update-docs.md

@@ -46,7 +46,7 @@ gh aw run update-docs
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration to configure documentation frameworks, documentation structure, themes, files, directories. Local configuration can be done in `.github/workflows/agentics/update-docs.config.md`.
 
 
 

docs/weekly-research.md

@@ -30,7 +30,7 @@ gh aw run weekly-research
 
 ## Configuration
 
-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`.
+This workflow requires no configuration and works out of the box. You can use local configuration 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.
 

workflows/daily-accessibility-review.md

@@ -18,13 +18,13 @@ safe-outputs:
   add-comment:
     discussion: true
     max: 5
-  github:
-    toolset: [all]
 
 tools:
   playwright:
   web-fetch:
   web-search:
+  github:
+    toolset: [all]
 
 timeout_minutes: 15
 

workflows/daily-test-improver.md

@@ -105,7 +105,7 @@ To decide which phase to perform:
 
    a. You can assume that the repository is in a state where the steps in `.github/actions/daily-test-improver/coverage-steps/action.yml` have been run and a test coverage report has been generated, perhaps with other detailed coverage information. Look at the steps in `.github/actions/daily-test-improver/coverage-steps/action.yml` to work out what has been run and where the coverage report should be, and find it. Also read any output files such as `coverage-steps.log` to understand what has been done. If the coverage steps failed, work out what needs to be fixed in `.github/actions/daily-test-improver/coverage-steps/action.yml` and make a pull request for those fixes and exit the entire workflow. If you can't find the coverage report, read a previous actions log for the run, or otherwise work out why the build or coverage generation failed by going through it step by step, then create an issue describing the problem. Only continue if you have a valid fresh coverage report.
 
-   b. Read the coverge report. Be detailed, looking to understand the files, functions, branches, and lines of code that are not covered by tests. Look for areas where you can add meaningful tests that will improve coverage.
+   b. Read the coverage report. Be detailed, looking to understand the files, functions, branches, and lines of code that are not covered by tests. Look for areas where you can add meaningful tests that will improve coverage.
 
    c. Check the most recent pull request with title starting with "${{ github.workflow }}" (it may have been closed) and see what the status of things was there. These are your notes from last time you did your work, and may include useful recommendations for future areas to work on.