Skip to content

Commit 939eb7b

Browse files
committed
add descriptions
1 parent 48413ac commit 939eb7b

15 files changed

Lines changed: 100 additions & 0 deletions

workflows/ci-doctor.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
11
---
2+
description: |
3+
This workflow is an automated CI failure investigator that triggers when monitored workflows fail.
4+
Performs deep analysis of GitHub Actions workflow failures to identify root causes,
5+
patterns, and provide actionable remediation steps. Analyzes logs, error messages,
6+
and workflow configuration to help diagnose and resolve CI issues efficiently.
7+
28
on:
39
workflow_run:
410
workflows: ["Daily Perf Improver", "Daily Test Coverage Improver"] # Monitor the CI workflow specifically

workflows/daily-accessibility-review.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
11
---
2+
description: |
3+
This workflow is an automated accessibility compliance checker for web applications.
4+
Reviews websites against WCAG 2.2 guidelines using Playwright browser automation.
5+
Identifies accessibility issues and creates GitHub discussions or issues with detailed
6+
findings and remediation recommendations. Helps maintain accessibility standards
7+
continuously throughout the development cycle.
8+
29
on:
310
schedule:
411
# Run daily at 3am UTC, all days except Saturday and Sunday

workflows/daily-backlog-burner.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
11
---
2+
description: |
3+
This workflow performs systematic backlog management by working through issues and pull requests.
4+
Operates in two phases: research entire backlog to categorize and prioritize items, then
5+
systematically close, resolve, or advance selected items. Creates discussions to track
6+
progress and gather maintainer feedback, helping reduce technical debt.
7+
28
on:
39
workflow_dispatch:
410
schedule:

workflows/daily-dependency-updates.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
11
---
2+
description: |
3+
This workflow performs automated dependency management by monitoring and updating project dependencies.
4+
Checks Dependabot alerts and updates dependencies in package manifests (not just lock files).
5+
Bundles multiple compatible updates into single pull requests, runs tests to verify
6+
compatibility, and creates draft PRs with working changes. Documents investigation
7+
attempts for problematic updates.
8+
29
on:
310
workflow_dispatch:
411
schedule:

workflows/daily-perf-improver.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
11
---
2+
description: |
3+
This workflow makes performance optimizations by identifying and improving application bottlenecks.
4+
It builds the project and analyzes performance metrics to find optimization opportunities.
5+
Operates in three phases: research performance landscape and create plan, infer build steps
6+
and create performance engineering guides, then implement optimizations and measure impact.
7+
Creates discussions to coordinate and draft PRs with improvements.
8+
29
on:
310
workflow_dispatch:
411
schedule:

workflows/daily-plan.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
11
---
2+
description: |
3+
This workflow performs strategic project planning by maintaining and updating the project roadmap.
4+
Analyzes repository state including open issues, PRs, and completed work to formulate
5+
a comprehensive project plan. Creates or updates a planning discussion with prioritized
6+
tasks, dependencies, and suggested new issues (via gh commands but doesn't create them).
7+
Incorporates maintainer feedback from comments on the plan.
8+
29
# Run once a day at midnight UTC
310
on:
411
schedule:

workflows/daily-progress.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
11
---
2+
description: |
3+
This workflow systematically delivers features from the project plan.
4+
Operates in two phases: research roadmap and feature landscape to create prioritized plan,
5+
then implement selected high-priority features via pull requests. Creates discussions to
6+
coordinate with maintainers and advance the project toward its strategic goals.
7+
28
on:
39
workflow_dispatch:
410
schedule:

workflows/daily-qa.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
11
---
2+
description: |
3+
This workflow performs adhoc quality assurance by validating project health daily.
4+
Checks that code builds and runs, tests pass, documentation is clear, and code
5+
is well-structured. Creates discussions for findings and can submit draft PRs
6+
with improvements. Provides continuous quality monitoring throughout development.
7+
28
on:
39
schedule:
410
# Run daily at 3am UTC, all days except Saturday and Sunday

workflows/daily-team-status.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,11 @@
11
---
2+
description: |
3+
This workflow created daily team status reporter creating upbeat activity summaries.
4+
Gathers recent repository activity (issues, PRs, discussions, releases, code changes)
5+
and generates engaging GitHub discussions with productivity insights, community
6+
highlights, and project recommendations. Uses a positive, encouraging tone with
7+
moderate emoji usage to boost team morale.
8+
29
on:
310
schedule:
411
# Every day at 9am UTC, all days except Saturday and Sunday

workflows/daily-test-improver.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,10 @@
11
---
2+
description: |
3+
This workflow performs test enhancements by systematically improving test quality and coverage.
4+
Operates in three phases: research testing landscape and create coverage plan, infer build
5+
and coverage steps, then implement new tests targeting untested code. Generates coverage
6+
reports, identifies gaps, creates comprehensive test suites, and submits draft PRs.
7+
28
on:
39
workflow_dispatch:
410
schedule:

0 commit comments

Comments
 (0)