docs: migrate repository guidance to Gitea
This commit is contained in:
1 parent
0d900fd72d
commit
7d60157863
31 files changed
+180
-102
No files matched your search
@@ -35,7 +35,7 @@ Inspect `git status --short` and distinguish pre-existing user changes from task
|
||||
Look for the originating spec, in this order:
|
||||
|
||||
1. The user's explicit spec, ticket, path, or acceptance criteria in the conversation. Preserve it as authoritative even when commits reference other work.
|
||||
2. Issue/MR references in relevant commit messages — fetch via `docs/agents/issue-tracker.md` when no explicit source was supplied.
|
||||
2. Issue/PR references in relevant commit messages — fetch via `docs/agents/issue-tracker.md` when no explicit source was supplied.
|
||||
3. A PRD/spec file under `docs/`, `specs/`, or `.scratch/` matching the branch name or feature.
|
||||
4. If nothing is found or the source is inaccessible, continue the Standards review and report the Spec coverage limitation. Ask for a source only when needed to answer the user's request; do not invent requirements or require tracker setup.
|
||||
|
||||
|
||||
Reference in new issue
Block a user