thatgfsj-code 1.0.3 → 3.0.0

package/src/skills/triage.ts

@@ -1,35 +1,35 @@
-import type { Skill } from './index.js';
-
-export const triageSkill: Skill = {
-  id: 'triage',
-  name: 'Issue Triage',
-  description: 'Quickly diagnose and prioritize issues',
-  category: 'debugging',
-  autoActivate: ['issue', 'problem', 'not working', 'broken', '不工作', '挂了'],
-  prompt: `## Issue Triage
-
-When something is broken, quickly assess:
-
-### Severity Classification
-- **P0 Critical**: System down, data loss, security breach
-- **P1 High**: Major feature broken, no workaround
-- **P2 Medium**: Feature degraded, workaround exists
-- **P3 Low**: Minor issue, cosmetic, nice-to-have
-
-### Quick Diagnosis
-1. **What changed?** - Recent commits, deployments, config changes
-2. **Who is affected?** - All users, some users, specific environment
-3. **When did it start?** - Timeline of first occurrence
-4. **What's the impact?** - Data loss, functionality, UX
-
-### Triage Output
-\`\`\`
-## Triage: [Issue Title]
-
-**Severity**: P1 High
-**Impact**: [who/what is affected]
-**Root Cause**: [best guess based on evidence]
-**Suggested Fix**: [minimal fix approach]
-**Workaround**: [if any]
-\`\`\``,
-};
+import type { Skill } from './index.js';
+
+export const triageSkill: Skill = {
+  id: 'triage',
+  name: 'Issue Triage',
+  description: 'Quickly diagnose and prioritize issues',
+  category: 'debugging',
+  autoActivate: ['issue', 'problem', 'not working', 'broken', '不工作', '挂了'],
+  prompt: `## Issue Triage
+
+When something is broken, quickly assess:
+
+### Severity Classification
+- **P0 Critical**: System down, data loss, security breach
+- **P1 High**: Major feature broken, no workaround
+- **P2 Medium**: Feature degraded, workaround exists
+- **P3 Low**: Minor issue, cosmetic, nice-to-have
+
+### Quick Diagnosis
+1. **What changed?** - Recent commits, deployments, config changes
+2. **Who is affected?** - All users, some users, specific environment
+3. **When did it start?** - Timeline of first occurrence
+4. **What's the impact?** - Data loss, functionality, UX
+
+### Triage Output
+\`\`\`
+## Triage: [Issue Title]
+
+**Severity**: P1 High
+**Impact**: [who/what is affected]
+**Root Cause**: [best guess based on evidence]
+**Suggested Fix**: [minimal fix approach]
+**Workaround**: [if any]
+\`\`\``,
+};

package/src/skills/verification.ts

@@ -1,31 +1,31 @@
-import type { Skill } from './index.js';
-
-export const verificationSkill: Skill = {
-  id: 'verification',
-  name: 'Verification Before Completion',
-  description: 'Always verify work before marking as done',
-  category: 'workflow',
-  prompt: `## Verification Protocol
-
-Before saying "done", always verify:
-
-### For Code Changes
-1. **Read the file** - Confirm the change was actually saved
-2. **Check syntax** - Make sure there are no syntax errors
-3. **Run tests** - If tests exist, run them
-4. **Check imports** - Verify all imports resolve
-
-### For File Operations
-1. **Verify file exists** - Check the file was created/modified
-2. **Read it back** - Confirm the content is correct
-3. **Check permissions** - Ensure the file is accessible
-
-### For Commands
-1. **Check exit code** - Was it 0?
-2. **Read output** - Look for warnings or errors
-3. **Verify side effects** - Did the command do what was expected?
-
-### Never Say "Done" Without
-- Seeing actual output confirming success
-- Or running a verification command`,
-};
+import type { Skill } from './index.js';
+
+export const verificationSkill: Skill = {
+  id: 'verification',
+  name: 'Verification Before Completion',
+  description: 'Always verify work before marking as done',
+  category: 'workflow',
+  prompt: `## Verification Protocol
+
+Before saying "done", always verify:
+
+### For Code Changes
+1. **Read the file** - Confirm the change was actually saved
+2. **Check syntax** - Make sure there are no syntax errors
+3. **Run tests** - If tests exist, run them
+4. **Check imports** - Verify all imports resolve
+
+### For File Operations
+1. **Verify file exists** - Check the file was created/modified
+2. **Read it back** - Confirm the content is correct
+3. **Check permissions** - Ensure the file is accessible
+
+### For Commands
+1. **Check exit code** - Was it 0?
+2. **Read output** - Look for warnings or errors
+3. **Verify side effects** - Did the command do what was expected?
+
+### Never Say "Done" Without
+- Seeing actual output confirming success
+- Or running a verification command`,
+};

package/src/skills/writing-plans.ts

@@ -1,42 +1,42 @@
-import type { Skill } from './index.js';
-
-export const writingPlansSkill: Skill = {
-  id: 'writing-plans',
-  name: 'Writing Plans',
-  description: 'Break down complex tasks into step-by-step execution plans',
-  category: 'planning',
-  autoActivate: ['plan', '怎么实现', '如何做', '方案', '设计', '架构'],
-  prompt: `## Planning Mode
-
-When the user asks you to plan something or the task is complex:
-
-1. **Understand the goal** - Clarify what the user wants to achieve
-2. **Explore the codebase** - Read relevant files to understand context
-3. **Break it down** - Create a numbered list of concrete steps
-4. **Identify risks** - Note potential issues or blockers
-5. **Estimate complexity** - Mark steps as simple/medium/complex
-
-### Plan Format
-\`\`\`
-## Plan: [Task Description]
-
-### Context
-- What we know about the current state
-- Files/modules involved
-
-### Steps
-1. [Step description] (simple/medium/complex)
-2. [Step description]
-   - Sub-step if needed
-3. [Step description]
-
-### Risks
-- [Potential issue and mitigation]
-
-### Files to modify
-- path/to/file1.ts - [what changes]
-- path/to/file2.ts - [what changes]
-\`\`\`
-
-Always present the plan to the user before executing. Ask: "Should I proceed with this plan?"`,
-};
+import type { Skill } from './index.js';
+
+export const writingPlansSkill: Skill = {
+  id: 'writing-plans',
+  name: 'Writing Plans',
+  description: 'Break down complex tasks into step-by-step execution plans',
+  category: 'planning',
+  autoActivate: ['plan', '怎么实现', '如何做', '方案', '设计', '架构'],
+  prompt: `## Planning Mode
+
+When the user asks you to plan something or the task is complex:
+
+1. **Understand the goal** - Clarify what the user wants to achieve
+2. **Explore the codebase** - Read relevant files to understand context
+3. **Break it down** - Create a numbered list of concrete steps
+4. **Identify risks** - Note potential issues or blockers
+5. **Estimate complexity** - Mark steps as simple/medium/complex
+
+### Plan Format
+\`\`\`
+## Plan: [Task Description]
+
+### Context
+- What we know about the current state
+- Files/modules involved
+
+### Steps
+1. [Step description] (simple/medium/complex)
+2. [Step description]
+   - Sub-step if needed
+3. [Step description]
+
+### Risks
+- [Potential issue and mitigation]
+
+### Files to modify
+- path/to/file1.ts - [what changes]
+- path/to/file2.ts - [what changes]
+\`\`\`
+
+Always present the plan to the user before executing. Ask: "Should I proceed with this plan?"`,
+};