@scotthamilton77/sidekick 0.0.8-alpha.0 → 0.0.8-alpha.1
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/assets/sidekick/defaults/features/session-summary.defaults.yaml +7 -1
- package/assets/sidekick/prompts/resume-message.prompt.txt +1 -1
- package/assets/sidekick/prompts/session-summary.prompt.txt +4 -4
- package/assets/sidekick/prompts/snarky-message.prompt.txt +1 -1
- package/dist/bin.js +532 -179
- package/dist/daemon.js +389 -104
- package/package.json +1 -1
|
@@ -44,7 +44,13 @@ settings:
|
|
|
44
44
|
maxTitleWords: 8
|
|
45
45
|
|
|
46
46
|
# Maximum words for generated intent description
|
|
47
|
-
maxIntentWords:
|
|
47
|
+
maxIntentWords: 15
|
|
48
|
+
|
|
49
|
+
# Maximum words for snarky message generation
|
|
50
|
+
maxSnarkyWords: 20
|
|
51
|
+
|
|
52
|
+
# Maximum words for resume/welcome-back message generation
|
|
53
|
+
maxResumeWords: 20
|
|
48
54
|
|
|
49
55
|
# Enable snarky/humorous comments in summaries
|
|
50
56
|
snarkyMessages: true
|
|
@@ -14,10 +14,10 @@ Output JSON matching this exact schema:
|
|
|
14
14
|
|
|
15
15
|
```json
|
|
16
16
|
{
|
|
17
|
-
"session_title": "string, max
|
|
17
|
+
"session_title": "string, max {{maxTitleWords}} words",
|
|
18
18
|
"session_title_confidence": 0.0-1.0,
|
|
19
19
|
"session_title_key_phrases": ["optional", "array", "of", "key", "terms/phrases"],
|
|
20
|
-
"latest_intent": "string, max
|
|
20
|
+
"latest_intent": "string, max {{maxIntentWords}} words",
|
|
21
21
|
"latest_intent_confidence": 0.0-1.0,
|
|
22
22
|
"latest_intent_key_phrases": ["optional", "array"],
|
|
23
23
|
"pivot_detected": false
|
|
@@ -88,7 +88,7 @@ Set pivot_detected based on whether the user switched to a fundamentally differe
|
|
|
88
88
|
</pivot_detection>
|
|
89
89
|
|
|
90
90
|
<session_title_rules>
|
|
91
|
-
- Max
|
|
91
|
+
- Max {{maxTitleWords}} words - think "What would the JIRA epic or feature title be?"
|
|
92
92
|
- Focus on the epic/feature level, not individual tasks
|
|
93
93
|
- Write as if creating a ticket for the broader work being done
|
|
94
94
|
- Start with an action verb when possible: Fix, Add, Implement, Refactor, Debug, Update, Remove, Verify
|
|
@@ -98,7 +98,7 @@ Set pivot_detected based on whether the user switched to a fundamentally differe
|
|
|
98
98
|
</session_title_rules>
|
|
99
99
|
|
|
100
100
|
<latest_intent_rules>
|
|
101
|
-
- Max
|
|
101
|
+
- Max {{maxIntentWords}} words
|
|
102
102
|
- What the user wanted in their most recent USER messages (you may infer from ASSISTANT messages when the assistant provides clarity to the user's intent)
|
|
103
103
|
- Use context to interpret vague prompts ("do it", "yes", "continue")
|
|
104
104
|
- If multi-instruction, capture most relevant instructions to recent context
|
|
@@ -19,6 +19,6 @@ Guidelines:
|
|
|
19
19
|
- Be snarky but not mean-spirited
|
|
20
20
|
- Reference specific technical details when you can
|
|
21
21
|
- Focus on workflow quirks, not personal attacks
|
|
22
|
-
- Stay under
|
|
22
|
+
- Stay under {{maxSnarkyWords}} words
|
|
23
23
|
|
|
24
24
|
Output ONLY your comment, nothing else.
|