@markusylisiurunen/tau 0.2.29 → 0.2.30
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/dist/core/version.js +1 -1
- package/dist/starter/prompts/commit-all.md +3 -3
- package/dist/starter/prompts/commit-staged.md +3 -3
- package/dist/starter/prompts/plan.md +3 -3
- package/dist/starter/prompts/review-branch.md +3 -3
- package/dist/starter/prompts/review-current-changes.md +3 -3
- package/dist/starter/prompts/review-last-commit.md +3 -3
- package/dist/starter/prompts/rewrite-prompt.md +3 -3
- package/dist/starter/skills/code-review/SKILL.md +2 -2
- package/package.json +1 -1
package/dist/core/version.js
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
|
-
export const APP_VERSION = "0.2.
|
|
1
|
+
export const APP_VERSION = "0.2.30";
|
|
2
2
|
//# sourceMappingURL=version.js.map
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: commit-all
|
|
3
|
-
label: commit all changes
|
|
4
|
-
description: stage and commit all current changes with a concise, well-formed message
|
|
2
|
+
id: "commit-all"
|
|
3
|
+
label: "commit all changes"
|
|
4
|
+
description: "stage and commit all current changes with a concise, well-formed message"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
Run `git status --short` and `git diff HEAD` (set max output tokens to 32768). If the working tree is clean and there are no untracked files, say so and stop.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: commit-staged
|
|
3
|
-
label: commit staged changes
|
|
4
|
-
description: commit the current staged changes with a concise, well-formed message
|
|
2
|
+
id: "commit-staged"
|
|
3
|
+
label: "commit staged changes"
|
|
4
|
+
description: "commit the current staged changes with a concise, well-formed message"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
Run `git diff --staged` (set max output tokens to 32768). If nothing is staged, say so and stop.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: plan
|
|
3
|
-
label: plan a feature or change
|
|
4
|
-
description: create a step-by-step plan for implementing a feature or change
|
|
2
|
+
id: "plan"
|
|
3
|
+
label: "plan a feature or change"
|
|
4
|
+
description: "create a step-by-step plan for implementing a feature or change"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
You are a technical planner. Your job is to produce implementation plans, not implementations. You will explore, ask questions, and document a clear path forward, then stop.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: review-branch
|
|
3
|
-
label: code review of current branch
|
|
4
|
-
description: ask for a thorough code review for the current branch
|
|
2
|
+
id: "review-branch"
|
|
3
|
+
label: "code review of current branch"
|
|
4
|
+
description: "ask for a thorough code review for the current branch"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
Use @@skill:code-review. Think hard and be thorough. What to review: the current branch.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: review-current-changes
|
|
3
|
-
label: code review of current changes
|
|
4
|
-
description: ask for a thorough code review for the current changes
|
|
2
|
+
id: "review-current-changes"
|
|
3
|
+
label: "code review of current changes"
|
|
4
|
+
description: "ask for a thorough code review for the current changes"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
Use @@skill:code-review. Think hard and be thorough. What to review: the current changes.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: review-last-commit
|
|
3
|
-
label: code review of most recent commit
|
|
4
|
-
description: ask for a thorough code review for the most recent commit
|
|
2
|
+
id: "review-last-commit"
|
|
3
|
+
label: "code review of most recent commit"
|
|
4
|
+
description: "ask for a thorough code review for the most recent commit"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
Use @@skill:code-review. Think hard and be thorough. What to review: the most recent commit.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
|
-
id: rewrite-prompt
|
|
3
|
-
label: help with (re)writing a prompt
|
|
4
|
-
description: help improve a given prompt
|
|
2
|
+
id: "rewrite-prompt"
|
|
3
|
+
label: "help with (re)writing a prompt"
|
|
4
|
+
description: "help improve a given prompt"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
7
|
You are an expert prompt writer. Your job is to help users craft prompts that feel like guidance from a thoughtful colleague rather than instructions from a manual. Good prompts respect the reader's intelligence while giving them exactly the context they need to succeed.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
|
-
name: code-review
|
|
3
|
-
description: Conduct rigorous code review for git changes and return prioritized, actionable findings in a strict verdict/findings format. Trigger: explicit.
|
|
2
|
+
name: "code-review"
|
|
3
|
+
description: "Conduct rigorous code review for git changes and return prioritized, actionable findings in a strict verdict/findings format. Trigger: explicit."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
## Goal
|