@willbooster/agent-skills 1.27.2 → 1.28.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -0
- package/package.json +1 -1
- package/skills/submit-issue/SKILL.md +18 -0
package/README.md
CHANGED
|
@@ -40,6 +40,7 @@ bunx skills@latest add WillBooster/agent-skills --agent claude-code --agent code
|
|
|
40
40
|
| [`screenshot-claude`](skills/screenshot-claude/SKILL.md) / [`screenshot-codex`](skills/screenshot-codex/SKILL.md) / [`screenshot-gemini`](skills/screenshot-gemini/SKILL.md) | Yes | Take a page screenshot with a chosen agent. | `$screenshot-codex https://example.com "Pricing" "the comparison table"` |
|
|
41
41
|
| [`simplify-pr-claude`](skills/simplify-pr-claude/SKILL.md) / [`simplify-pr-codex`](skills/simplify-pr-codex/SKILL.md) / [`simplify-pr-gemini`](skills/simplify-pr-gemini/SKILL.md) | Yes | Simplify the current PR with a chosen agent. | `$simplify-pr-codex` |
|
|
42
42
|
| [`stabilize-tests`](skills/stabilize-tests/SKILL.md) | No | Stabilize flaky or unreliable tests. | `$stabilize-tests test/auth.e2e.test.ts` |
|
|
43
|
+
| [`submit-issue`](skills/submit-issue/SKILL.md) | No | Submit a GitHub issue after clarifying ambiguous specs. | `$submit-issue Add an export button to the reports page` |
|
|
43
44
|
| [`update-deps`](skills/update-deps/SKILL.md) | No | Update dependencies and complete the PR. | `$update-deps` |
|
|
44
45
|
| [`update-pr`](skills/update-pr/SKILL.md) | No | Update the PR title and body. | `$complete-pr then $update-pr` |
|
|
45
46
|
| [`wbfy`](skills/wbfy/SKILL.md) | No | Apply `wbfy` to the current repository. | `$wbfy` |
|
package/package.json
CHANGED
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: submit-issue
|
|
3
|
+
description: Submit a GitHub issue after inspecting the current code and clarifying ambiguous requirements with the user.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Submit issue workflow
|
|
7
|
+
|
|
8
|
+
1. Read the user's request, then inspect the current code enough to understand the affected behavior.
|
|
9
|
+
2. If the issue would be ambiguous after that inspection, ask the user concise clarification questions and stop.
|
|
10
|
+
3. Otherwise, create a GitHub issue from the discussion and code context, then report the issue URL.
|
|
11
|
+
|
|
12
|
+
The issue title must follow the Conventional Commits specification, such as `feat: concise issue title` or `fix: concise issue title`.
|
|
13
|
+
|
|
14
|
+
```bash
|
|
15
|
+
gh issue create --title "feat: concise issue title" --body-file - <<'EOF'
|
|
16
|
+
[Issue body]
|
|
17
|
+
EOF
|
|
18
|
+
```
|