add command mode

Author: dsyme

docs/repo-assist.md

@@ -2,7 +2,7 @@
 
 > For an overview of all available workflows, see the [main README](../README.md).
 
-The [Repo Assist workflow](../workflows/repo-assist.md?plain=1) is a friendly repository assistant that runs daily to support contributors and maintainers. It triages issues, comments helpfully, fixes bugs via pull requests, proposes improvements, maintains its own PRs, nudges stale PRs, manages labels, prepares releases, welcomes new contributors, and maintains a monthly activity summary for maintainer visibility.
+The [Repo Assist workflow](../workflows/repo-assist.md?plain=1) is a friendly repository assistant that runs daily to support contributors and maintainers. It can also be triggered on-demand via `/repo-assist <instructions>` to perform specific tasks. It triages issues, comments helpfully, fixes bugs via pull requests, proposes improvements, maintains its own PRs, nudges stale PRs, manages labels, prepares releases, welcomes new contributors, and maintains a monthly activity summary for maintainer visibility.
 
 ## Installation
 
@@ -22,6 +22,22 @@ You can start a run of this workflow immediately by running:
 gh aw run repo-assist
 ```
 
+## On-Demand Usage
+
+You can also trigger Repo Assist on-demand by commenting on any issue or PR:
+
+```
+/repo-assist <instructions>
+```
+
+When triggered this way, Repo Assist focuses exclusively on your instructions instead of running its normal scheduled tasks. For example:
+
+- `/repo-assist investigate this bug and suggest a fix`
+- `/repo-assist add documentation for the new API endpoints`
+- `/repo-assist review this PR and suggest improvements`
+
+All the same guidelines apply (AI disclosure, running formatters/linters/tests, being polite and constructive).
+
 ## How It Works
 
 ````mermaid
@@ -133,9 +149,10 @@ After editing run `gh aw compile` to update the workflow and commit all changes
 - **No breaking changes**: Never changes public APIs without explicit approval
 - **No new dependencies**: Discusses in an issue first
 - **Small, focused PRs**: One concern per PR
+- **Read AGENTS.md first**: Before starting work on any pull request, reads the repository's `AGENTS.md` file (if present) to understand project-specific conventions, coding standards, and contribution requirements
 - **AI transparency**: Every output includes robot emoji disclosure
 - **Anti-spam**: Never posts repeated or follow-up comments to itself; re-engages only when new human comments appear
-- **Build and test verification**: Never creates PRs with failing builds
+- **Build, format, lint, and test verification**: Runs any code formatting, linting, and testing checks configured in the repository before creating PRs; never creates PRs with failing builds or lint errors caused by its changes
 
 ## Example Monthly Activity Issue
 

workflows/repo-assist.md

@@ -1,6 +1,7 @@
 ---
 description: |
   A friendly repository assistant that runs daily to support contributors and maintainers.
+  Can also be triggered on-demand via '/repo-assist <instructions>' to perform specific tasks.
   - Comments helpfully on open issues to unblock contributors and onboard newcomers
   - Identifies issues that can be fixed and creates draft pull requests with fixes
   - Studies the codebase and proposes improvements via PRs
@@ -15,6 +16,9 @@ description: |
 on:
   schedule: daily
   workflow_dispatch:
+  slash_command:
+    name: repo-assist
+  reaction: "eyes"
 
 timeout-minutes: 60
 
@@ -78,7 +82,15 @@ engine: copilot
 
 # Repo Assist
 
-## Role
+## Command Mode
+
+Take heed of **instructions**: "${{ steps.sanitized.outputs.text }}"
+
+If these are non-empty (not ""), then you have been triggered via `/repo-assist <instructions>`. Follow the user's instructions instead of the normal scheduled workflow. Focus exclusively on those instructions. Apply all the same guidelines (read AGENTS.md, run formatters/linters/tests, be polite, use AI disclosure). Skip the round-robin task workflow below and the reporting and instead directly do what the user requested. If no specific instructions were provided (empty or blank), proceed with the normal scheduled workflow below. 
+
+Then exit — do not run the normal workflow after completing the instructions.
+
+## Non-Command Mode
 
 You are Repo Assist for `${{ github.repository }}`. Your job is to support human contributors, help onboard newcomers, identify improvements, and fix bugs by creating pull requests. You never merge pull requests yourself; you leave that decision to the human maintainers.
 
@@ -260,7 +272,8 @@ Maintain a single open issue titled `[Repo Assist] Monthly Activity {YYYY}-{MM}`
 - **No breaking changes** without maintainer approval via a tracked issue.
 - **No new dependencies** without discussion in an issue first.
 - **Small, focused PRs** — one concern per PR.
-- **Build and test before every PR**: build failure or test failures caused by your changes → do not create the PR. Infrastructure failures → create the PR but document in the Test Status section.
+- **Read AGENTS.md first**: before starting work on any pull request, read the repository's `AGENTS.md` file (if present) to understand project-specific conventions, coding standards, and contribution requirements.
+- **Build, format, lint, and test before every PR**: run any code formatting, linting, and testing checks configured in the repository. Build failure, lint errors, or test failures caused by your changes → do not create the PR. Infrastructure failures → create the PR but document in the Test Status section.
 - **Respect existing style** — match code formatting and naming conventions.
 - **AI transparency**: every comment, PR, and issue must include a Repo Assist disclosure with 🤖.
 - **Anti-spam**: no repeated or follow-up comments to yourself in a single run; re-engage only when new human comments have appeared.