File tree Expand file tree Collapse file tree 1 file changed +15
-12
lines changed
Expand file tree Collapse file tree 1 file changed +15
-12
lines changed Original file line number Diff line number Diff line change 1- # GitHub Issue Filing
1+ # File Issue in GitHub
2+
3+ ## Overview
4+
5+ The goal is to draft GitHub ticket as a markdown that can be copy pasted.
6+
7+ If avaialble use Github MCP.
8+
9+ ## Workflow
210
311When filing issues to i-am-bee/agentstack:
412
@@ -10,18 +18,13 @@ When filing issues to i-am-bee/agentstack:
1018
11193 . Ask the user to specify if something is unclear based on the template and their initial prompt.
1220
13- 4 . Before filing the ticket in github show the full ticket that you are about to file to have it confirmed by the user. Show this as a markdown.
21+ 4 . If available use Github MCP to search duplicates
1422
15- 5 . Use GitHub MCP tools to
16- - Find duplicate tickets
17- - File the ticket
23+ 5 . Before filing the ticket in github show the full ticket that you are about to file to have it confirmed by the user. Show this as a markdown.
1824
19- ## Rules for issue filing
20- - Keep the ticket extremely concise
21- - Don't provide implementation details. Your goal is to define the problem and its potential consequences, not to propose a solution.
22-
23- # TypeScript
25+ 6 . Once user is happy, you can either submit the ticket if GH MCP is available otherwise dump as markdown.
2426
25- ## Code Style
27+ ## Rules
2628
27- - preferably don't use single letter variable names, make it at least a bit descriptive
29+ - Keep the ticket extremely concise
30+ - Don't provide implementation details. Your goal is to define the problem and its potential consequences, not to propose a solution.
You can’t perform that action at this time.
0 commit comments