steve/skills
Public Access
1
0
Fork 0
Code Issues 11 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

docs(setup-skills): add Gitea forge write safety rules

Browse Source 
tea --description does not read stdin via @-, so a piped heredoc silently
creates an issue whose body is the literal "@-". Document the command-
substitution form, a post-create body check, and inspecting tea --help
before relying on CLI syntax.
This commit is contained in:
gitadmin
2026-09-25 13:16:09 -04:00
parent dab262ac23
commit 53da2f7094
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/setup-skills/issue-tracker-gitea.md
+9
View File
@@ -13,6 +13,15 @@ Issues and PRDs for this repo live as Gitea issues. Use the `tea` CLI for all op
Infer the repo from git remote -v — `tea` does this automatically when run inside a clone. Infer the repo from git remote -v — `tea` does this automatically when run inside a clone.
### Forge write safety
- `tea --description` does not read stdin via `@-`; never use `--description @-`.
- Pass multiline descriptions with shell command substitution:
`tea issue create --description "$(cat <<'EOF' ... EOF)"`
- After every issue create/edit, verify:
`tea issue <n> -o json | jq -e '.body != "" and .body != "@-" and (.body | contains("## Question"))'`
- Inspect `tea --help` before relying on CLI syntax.
## Pull requests as a triage surface ## Pull requests as a triage surface
**PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_ **PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_