anthony.wen/cds-ai
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove galaxy-complete issue workflow instructions from AGENTS.md

Browse Source 
Remove the old issue-handling defaults and approval rules that referred
to the galaxy-complete workspace.

Keep the remaining commit approval and repository safety guidance.
This commit is contained in:
anthony.wen
2026-04-13 18:48:34 -04:00
parent 7ffe0d9e76
commit e801fd3b6b
1 changed files with 0 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
AGENTS.md
View File

@@ -2,23 +2,6 @@
This document provides workspace-level instructions for AI agents working anywhere under `/home/aw/code/cds`. This document provides workspace-level instructions for AI agents working anywhere under `/home/aw/code/cds`.
## Default Issue Repository
When the user asks to create an issue, or uses any reasonable variation of that request, default to the `galaxy-complete` workspace at `/home/aw/code/cds/galaxy-complete` unless the user explicitly says otherwise.
## Issue Creation Preferences
When the user asks to create an issue:
1. If the user says to include attached files, attached screenshots, or references recent screenshots/files, always look in `/home/aw/code/cds/screenshots` as the intended location for attachments unless the user explicitly says otherwise.
2. Do not ask the user to identify the files again when the request is to include files, attachments, screenshots, or recent files, because the default attachment location is already defined above unless the user says otherwise.
3. Always prepare the issue draft for user review before submitting it, and wait for explicit approval before creating the issue.
4. Unless the user says otherwise, assume the intended labels are `qa:reported` and `bug`.
## Galaxy Complete Issue Approval
For work in `/home/aw/code/cds/galaxy-complete`, always let the user review the proposed issue report first and wait for the user's explicit approval before creating, submitting, editing, updating, commenting on, labeling, attaching files to, closing, reopening, deleting, or otherwise changing any issue or issue-related content.
## Commit Approval ## Commit Approval
Always let the user review the proposed commit scope and commit message first, and wait for the user's explicit approval before creating any local git commit in this workspace. Always let the user review the proposed commit scope and commit message first, and wait for the user's explicit approval before creating any local git commit in this workspace.