vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1

docs, prompts, hive-forge: stop handing readers the renamed verbs

Browse source 
docs/tools/forge.md already listed the nine renamed verbs as removed, then
used them ~30 more times in pasteable blocks. Sweeps every occurrence a
reader would type, including three runtime messages that told the user to
run a verb the same binary rejects.

The renamed-verb list itself keeps the old names; it is what documents them.

Refs #4155
This commit is contained in:
atlas 2026-09-10 15:56:20 +02:00 • committed by mara
commit 55f01942a2
23 changed files with 73 additions and 73 deletions
Download patch file Download diff file Expand all files Collapse all files

8
claude-plugins/plugins/base/skills/forge-issue-filing/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: forge-issue-filing
description: How to file a well-formed forge issue through the hive-forge CLI - check for an existing duplicate first (title-only grepping misses it, use server-side --search), pick a title that states the problem not the symptom, write a body that's the *problem*, and put any proposed fix in a follow-up comment rather than the issue description. Use this whenever you're about to run `hive-forge issue-create`, whenever you hit a bug/gap/usability problem and are about to file it rather than silently work around it, or whenever asked to write up a finding as an issue.
description: How to file a well-formed forge issue through the hive-forge CLI - check for an existing duplicate first (title-only grepping misses it, use server-side --search), pick a title that states the problem not the symptom, write a body that's the *problem*, and put any proposed fix in a follow-up comment rather than the issue description. Use this whenever you're about to run `hive-forge issue create`, whenever you hit a bug/gap/usability problem and are about to file it rather than silently work around it, or whenever asked to write up a finding as an issue.
---
# Forge Issue Filing
@ -55,7 +55,7 @@ proposed implementation - post that as a **follow-up comment**, not baked
into the description:
```sh
hive-forge issue-create --title "..." --body "..." --label ... --assignee ...
hive-forge issue create --title "..." --body "..." --label ... --assignee ...
hive-forge comment <number> --body "proposed fix: ..."
```
@ -74,7 +74,7 @@ separate from the problem statement.
## 4. Labels: check the taxonomy, don't guess
Label names are repo-specific and an unresolved name in `issue-create
Label names are repo-specific and an unresolved name in `issue create
--label` errors out before the issue is even created (better than the
alternative, but still wasted effort if you guess wrong). If you don't
already know the repo's label scopes, list them first:
@ -107,7 +107,7 @@ unassigned and let it surface through the normal triage sweep (see the
```sh
hive-forge list --search "thing you think is broken" --state all # 1: dedup
hive-forge repo-labels # 4: taxonomy
hive-forge issue-create \
hive-forge issue create \
--title "the problem, stated durably" \
--body "what's wrong, how to reproduce, where it bites" \
--label area/whatever --label type/bug