@witty-ai/skill-insight 0.5.0-beta → 0.6.0-beta

package/.next/standalone/eslint.config.mjs

@@ -1,18 +0,0 @@
-import { defineConfig, globalIgnores } from "eslint/config";
-import nextVitals from "eslint-config-next/core-web-vitals";
-import nextTs from "eslint-config-next/typescript";
-
-const eslintConfig = defineConfig([
-  ...nextVitals,
-  ...nextTs,
-  // Override default ignores of eslint-config-next.
-  globalIgnores([
-    // Default ignores of eslint-config-next:
-    ".next/**",
-    "out/**",
-    "build/**",
-    "next-env.d.ts",
-  ]),
-]);
-
-export default eslintConfig;

package/.next/standalone/features/feature-skill-used-jump-link/design/2026-03-18-skill-used-jump-link-design.md

@@ -1,126 +0,0 @@
-# Design: Skill Used Jump Link Feature
-
-**Issue**: #52  
-**Date**: 2026-03-18  
-**Status**: Design Approved
-
-## Overview
-
-Add click-to-navigate functionality to the "skill used" field in execution records, allowing users to click skill names and navigate to a dedicated skill detail page.
-
-## Requirements
-
-1. Clickable skill names in execution records
-2. Visual link styling (color, underline, hover effects)
-3. Navigate to skill detail page with specific version
-4. Support multiple skills in one record
-5. Graceful error handling for deleted/non-existent skills
-
-## Architecture
-
-```
-Execution Records (details/page.tsx)
-        │
-        │ click skill name
-        ▼
-/skills/[id]?version=[version]  ← New Page
-        │
-        ▼
-SkillDetailPage
-  - Skill metadata (name, description, version)
-  - Flow diagram (Mermaid)
-  - Back navigation
-```
-
-## Components
-
-### 1. SkillLink Component
-
-**Path**: `/src/components/SkillLink.tsx`
-
-```typescript
-interface SkillLinkProps {
-  skillId: string | null | undefined;
-  skillName: string;
-  version?: string | number;
-}
-```
-
-**Features**:
-- Styled as clickable link (blue color, underline on hover)
-- Navigates to `/skills/{skillId}?version={version}`
-- Falls back to plain text if skillId missing
-- Shows tooltip for missing skillId
-
-### 2. Skill Detail Page
-
-**Path**: `/src/app/skills/[id]/page.tsx`
-
-**Features**:
-- Fetches skill via `GET /api/skills/{id}/versions/{version}`
-- Displays: skill name, description, version, flow diagram
-- Uses existing SkillVersionDetailModal content as reference
-- Back navigation button
-- Error state for skill not found
-
-### 3. Modified Files
-
-| File | Changes |
-|------|---------|
-| `src/app/details/page.tsx` | Replace skill used text with SkillLink components |
-| `src/components/Dashboard.tsx` | Add SkillLink if skills shown in list view |
-
-## URL Format
-
-```
-/skills/{skillId}?version={versionNumber}
-```
-
-Examples:
-- `/skills/skill_my-skill_12345?version=1`
-- `/skills/skill_my-skill_12345` (no version = latest)
-
-## Error Handling
-
-| Scenario | Behavior |
-|----------|----------|
-| Skill deleted | Show "Skill not found" page with back button |
-| Invalid version | Fall back to latest version |
-| Missing skillId | Render plain text with tooltip |
-| API error | Show error message with retry option |
-
-## Data Flow
-
-1. User views execution record with skill used field
-2. SkillName rendered as `<SkillLink>` component
-3. User clicks skill name
-4. Navigate to `/skills/[id]?version=[version]`
-5. Page fetches skill data via API
-6. Display skill details with flow diagram
-
-## Testing Strategy
-
-### Unit Tests
-- SkillLink component rendering
-- Navigation URL generation
-- Error state handling
-
-### Integration Tests
-- Click skill → navigate to detail page
-- Skill detail page data fetching
-- Error scenarios (deleted skill, invalid version)
-
-### Manual Tests
-- Visual styling verification
-- Multiple skills display
-- Back navigation
-
-## Implementation Tasks
-
-1. Create SkillLink component
-2. Create skill detail page route
-3. Create skill detail page component
-4. Modify details page to use SkillLink
-5. Add error handling
-6. Write tests
-7. Verify all acceptance criteria

package/.next/standalone/features/feature-skill-used-jump-link/feature.json

@@ -1,32 +0,0 @@
-{
-  "name": "skill-used-jump-link",
-  "title": "执行记录中skill used增加跳转功能",
-  "status": "completed",
-  "claimedBy": "gongxh13",
-  "claimedAt": "2026-03-18T08:50:00Z",
-  "completedAt": "2026-03-18T09:30:00Z",
-  "worktree": {
-    "path": "",
-    "enabled": false
-  },
-  "platformIssue": {
-    "id": 52,
-    "web_url": "https://atomgit.com/openeuler/witty-skill-insight/issues/52",
-    "title": "【feature】执行记录中skill used增加跳转功能",
-    "state": "open"
-  },
-  "documentation": {
-    "requirements": [],
-    "design": [],
-    "tests": [],
-    "pr": [
-      {
-        "title": "Pull Request #38",
-        "url": "https://atomgit.com/openeuler/witty-skill-insight/merge_requests/38",
-        "createdAt": "2026-03-18T09:30:00Z"
-      }
-    ],
-    "deployment": [],
-    "notes": ""
-  }
-}

package/.next/standalone/features/feature-skill-used-jump-link/issue.md

@@ -1,32 +0,0 @@
-#52: 【feature】执行记录中skill used增加跳转功能
-状态: open | 创建: 2026-03-10 | 更新: 2026-03-13
-标签: sig/sig-intelligence
-链接: https://atomgit.com/openeuler/witty-skill-insight/issues/52
-
---- Issue Content ---
-**1、背景与价值**
-在Witty-Skill-Insight平台中，执行记录中的skill used字段当前仅以字符串形式显示，展示实际执行过程中使用的skill名称。用户无法直接从执行记录跳转到对应的skill详情页面查看skill的完整信息。增加跳转功能可以让用户快速查看skill详情，提升使用体验和操作效率。
-
-**2、需求详情**
-- 跳转功能：在执行记录的skill used字段上增加点击跳转功能
-- 跳转目标：点击skill名字后跳转到对应的skill详情页面
-- 视觉提示：将skill used字符串改为可点击的链接样式，添加适当的视觉提示（如颜色、下划线、hover效果）
-- 保持显示：跳转功能不改变skill used的显示内容，仍然显示实际执行的skill名称
-- 多skill支持：如果执行记录中有多个skill，每个skill都应该支持跳转
-- 错误处理：如果skill不存在或已被删除，提供友好的错误提示
-
-**3、验收标准**
-一：跳转功能正常
-点击skill used字段中的skill名称能够正确跳转到对应的skill详情页面。
-
-二：视觉提示清晰
-skill名称有明显的可点击样式提示，用户能够识别这是可跳转的链接。
-
-三：显示内容不变
-跳转功能不改变skill used字段的显示内容，仍然显示实际执行的skill名称。
-
-四：多skill支持
-如果执行记录中有多个skill，每个skill都能正确跳转到对应的详情页面。
-
-五：错误处理友好
-当skill不存在或已被删除时，能够提供友好的错误提示。