@hurshb50/setup-ubuntu 2.0.0 → 2.0.2

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.
@@ -1,18 +1,19 @@
1
1
  ---
2
2
  name: code-dependency-graph
3
- description: Trace what a selected code section uses and what uses it.
4
- disable-model-invocation: true
3
+ description: Show lines in selected code that use dependencies.
5
4
  ---
6
5
 
7
- # Code Dependency Graph
6
+ # Code Dependencies
8
7
 
9
- Trace dependencies for the selected code section.
8
+ For each direct dependency used by the selected code:
10
9
 
11
- ## The graph
10
+ - Show the relevant selected-code line or short snippet.
11
+ - Name the dependency and briefly explain it for a beginner.
12
+ - Explain what role it plays in this code.
12
13
 
13
- - Inspect the code and its references
14
- - Show what the section depends on
15
- - Show what depends on the section
16
- - Use `A → B` to mean “B uses A”
17
- - Show direct relationships, not guesses
18
- - Mark dependencies outside the requested scope
14
+ Use plain language. Assume the reader is unfamiliar with the terms.
15
+ Keep explanations brief and focused on the selected code.
16
+ Include file locations when available.
17
+ Do not show dependency definitions or trace callers.
18
+ Do not add diagrams or unrelated context.
19
+ Output only the dependency snippets and explanations.
@@ -1,7 +1,6 @@
1
1
  ---
2
2
  name: design-api
3
3
  description: Push an architecture forward. Interview me, fan out on widely varying designs, then build the API shape together.
4
- disable-model-invocation: true
5
4
  ---
6
5
 
7
6
  # Design API
@@ -0,0 +1,45 @@
1
+ ---
2
+ name: draft-pr
3
+ description: Create draft pull requests while preserving Git stack structure.
4
+ ---
5
+
6
+ # Draft PR
7
+
8
+ Create draft PRs using repository conventions.
9
+
10
+ ## Relevant commands
11
+
12
+ - `gh pr list`: Find nearby PRs.
13
+ - `gh pr view`: Inspect PR details.
14
+ - `gh pr create --draft`: Create a draft.
15
+ - `gh pr edit`: Update PR details.
16
+ - `gh pr ready --undo`: Restore draft status.
17
+ - `gh stack view`: Inspect the stack.
18
+ - `gh stack link`: Link existing PRs.
19
+ - `gh stack rebase`: Rebase stack branches.
20
+ - `gh stack push`: Push stack branches.
21
+ - `gh stack submit`: Create or update stack PRs.
22
+
23
+ Check `gh --help`, `gh pr --help`, or `gh stack --help` when needed. Check subcommand help before using unfamiliar options.
24
+
25
+ ## Draft status
26
+
27
+ Draft status belongs to each PR, not its stack.
28
+
29
+ - Draft only PRs explicitly requested as drafts.
30
+ - Preserve every existing PR's current status.
31
+ - Never convert an entire stack to drafts.
32
+ - Before stack commands, verify their draft-status behavior.
33
+ - Ask before any command could change other PR statuses.
34
+
35
+ ## Workflow
36
+
37
+ - Inspect branch and working-tree state.
38
+ - Identify the intended base branch.
39
+ - Review nearby PR titles and descriptions.
40
+ - Split changes into stacked PRs when requested.
41
+ - Preserve user changes and uncommitted work.
42
+ - Ask before committing changes.
43
+ - Do not use `gh stack submit` unless requested.
44
+ - Verify titles, bases, and draft status.
45
+ - Report PRs and stack links.
@@ -1,18 +1,14 @@
1
1
  ---
2
2
  name: explain-code
3
- description: Explain a selected code section to someone learning it.
4
- disable-model-invocation: true
3
+ description: Explain all implementation code in the selected scope to someone learning it.
5
4
  ---
6
5
 
7
6
  # Explain Code
8
7
 
9
- Explain one selected section of code.
8
+ Explain all implementation code in scope for a beginner.
10
9
 
11
- Assume no prior knowledge.
12
-
13
- ## The explanation
14
-
15
- - Define technical terms before using them
16
- - Explain purpose, inputs, output, and behavior
17
- - Stay within the selected section
18
- - Verify details against the code
10
+ - Cover every implementation part in scope; split large scopes into ordered chunks.
11
+ - Explain each chunk's code, purpose, behavior, and connections.
12
+ - Trace execution and data flow; verify context and define unfamiliar terms.
13
+ - In every chunk, include a concrete example tracing temporary values step by step.
14
+ - Exclude tests/configuration; output the complete explanation only.
@@ -1,7 +1,6 @@
1
1
  ---
2
2
  name: rephrase-last-message
3
3
  description: Rephrase the last agent message without changing its meaning.
4
- disable-model-invocation: true
5
4
  ---
6
5
 
7
6
  # Rephrase Last Message
@@ -1,7 +1,6 @@
1
1
  ---
2
2
  name: teach-concept
3
3
  description: Teach me a concept from the ground up.
4
- disable-model-invocation: true
5
4
  ---
6
5
 
7
6
  # Teach Concept
@@ -0,0 +1,20 @@
1
+ ---
2
+ name: test-planning
3
+ description: Plan reliable, behavior-focused tests without implementing them.
4
+ ---
5
+
6
+ # Test Planning
7
+
8
+ Plan tests for a selected function or class.
9
+
10
+ - Inspect behavior and relevant callers.
11
+ - Check nearby tests for conventions.
12
+ - Focus on observable outcomes.
13
+ - Suggest representative inputs and expected results.
14
+ - Include important edge cases and errors.
15
+ - Identify uncontrolled or nondeterministic inputs.
16
+ - Recommend ways to control relevant inputs.
17
+ - Avoid implementation-detail tests.
18
+ - Avoid redundant cases and brittle assertions.
19
+ - Do not write or edit tests.
20
+ - Return a concise test plan.
@@ -9,7 +9,7 @@
9
9
  },
10
10
  "enable_feedback": false,
11
11
  "notify_when_agent_waiting": "never",
12
- "sandbox_permissions": { "allow_all_hosts": true, "allow_fs_write_all": true },
12
+ "sandbox_permissions": { "allow_unsandboxed": true, "allow_all_hosts": true, "allow_fs_write_all": true },
13
13
  "thinking_display": "always_collapsed",
14
14
  "tool_permissions": { "default": "allow" }
15
15
  },
@@ -11,7 +11,7 @@ import util from "util";
11
11
  import childProcess from "child_process";
12
12
  //#region package.json
13
13
  var name = "@hurshb50/setup-ubuntu";
14
- var version = "1.5.3";
14
+ var version = "2.0.1";
15
15
  //#endregion
16
16
  //#region source/modules/logger/logger.ts
17
17
  var Logger = class Logger {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@hurshb50/setup-ubuntu",
3
- "version": "2.0.0",
3
+ "version": "2.0.2",
4
4
  "type": "module",
5
5
  "files": [
6
6
  "distribution"