ai-developer-skill-os 7.5.0 → 8.1.4

package/skills/_archive_old_skills/qk-git-engineer/SKILL.md

@@ -1,304 +0,0 @@
----
-name: qk-git-engineer
-description: >-
-  Viết commit message chuẩn Conventional Commits, mô tả Pull Request, Changelog và Release Notes chuyên nghiệp.
-version: 1.0.0
-category: engineering
-tags: [git, commit, pull-request, changelog, release, conventional-commits]
-platforms: [antigravity, claude-code, kilo-code, cursor, windsurf]
----
-
-# Git Engineer
-
-> **Language rule:**
-> Use English for: code, identifiers, file names, architecture terms, technical decisions.
-> Use the user's language for: explanations, questions, summaries, and feedback.
-> The user may write in any language — detect and match it automatically.
-
-> 📌 **Standard followed:** [Conventional Commits v1.0.0](https://www.conventionalcommits.org/)
-
----
-
-## Trigger
-
-Activate this skill when:
-- User wants to write a commit message
-- User has finished a feature and needs a PR description
-- User needs to generate a changelog for a release
-- User asks "what should I commit?", "write PR", "release notes"
-- User wants to clean up their git history before merging
-
----
-
-## Scope
-
-- ✅ Write commit messages (Conventional Commits format)
-- ✅ Suggest logical commit groupings from a set of changes
-- ✅ Write pull request titles and descriptions
-- ✅ Generate CHANGELOG entries from commit history
-- ✅ Write release notes (human-readable)
-- ✅ Suggest branch naming conventions
-- ✅ Review and improve existing commit messages
-
----
-
-## Non-goals
-
-- ❌ Do NOT run git commands without explicit user approval
-- ❌ Do NOT force-push or rebase without warning
-- ❌ Do NOT create commits that bundle unrelated changes
-- ❌ Do NOT write vague messages like "fix stuff" or "updates"
-
----
-
-## Conventional Commits Format
-
-```
-<type>(<scope>): <description>
-
-[optional body]
-
-[optional footer(s)]
-```
-
-### Types
-
-| Type | When to use |
-|------|-------------|
-| `feat` | New feature |
-| `fix` | Bug fix |
-| `docs` | Documentation only changes |
-| `style` | Formatting, missing semicolons — no logic change |
-| `refactor` | Code restructure without behavior change |
-| `perf` | Performance improvement |
-| `test` | Adding or fixing tests |
-| `build` | Build system or dependency changes |
-| `ci` | CI/CD configuration changes |
-| `chore` | Other changes that don't modify src or test files |
-| `revert` | Reverts a previous commit |
-
-### Breaking Changes
-
-```
-feat!: remove deprecated login endpoint
-
-BREAKING CHANGE: The /auth/login endpoint has been removed.
-Use /auth/v2/login instead.
-```
-
----
-
-## Workflow
-
-### Phase 1 — Understand the Changes
-
-Review what has changed:
-1. Read the diff or file list provided by the user
-2. Group changes by concern (feature, fix, refactor, docs, etc.)
-3. Identify if changes should be split into multiple commits or kept as one
-4. Note any breaking changes
-
----
-
-### Phase 2 — Commit Message(s)
-
-For each logical group of changes, write:
-
-**Single commit:**
-```
-feat(auth): add refresh token rotation
-
-Implements automatic refresh token rotation on each use.
-Old tokens are invalidated immediately after use to prevent
-replay attacks.
-
-Closes #142
-```
-
-**Multiple commits (if changes should be split):**
-```
-refactor(api): extract axios instance to lib/axios.ts
-
-No behavior change — prepares for interceptor configuration.
-
----
-
-feat(api): add request retry interceptor
-
-Automatically retries failed requests up to 3 times with
-exponential backoff. Skips retry for 4xx errors.
-```
-
-**Rules:**
-- Subject line: ≤72 characters, imperative mood ("add" not "added")
-- Body: explain *why*, not *what* (the diff shows what)
-- Reference issues: `Closes #123`, `Fixes #456`, `Refs #789`
-
----
-
-### Phase 3 — Pull Request Description
-
-Structure:
-```markdown
-## Summary
-[1-3 sentences describing what this PR does and why]
-
-## Changes
-- [Specific change 1]
-- [Specific change 2]
-- [Specific change 3]
-
-## Testing
-- [ ] Unit tests pass
-- [ ] Manual testing: [describe what you tested]
-- [ ] [Other relevant checks]
-
-## Breaking Changes
-[None | Description of breaking change and migration path]
-
-## Screenshots / Demo
-[If UI changes — attach before/after screenshots]
-
-## Related Issues
-Closes #[issue number]
-```
-
----
-
-### Phase 4 — Changelog Entry
-
-Follow [Keep a Changelog](https://keepachangelog.com/) format:
-
-```markdown
-## [1.2.0] - 2026-07-01
-
-### Added
-- Refresh token rotation for improved security (#142)
-- Retry interceptor with exponential backoff (#138)
-
-### Changed
-- Extracted axios instance to `src/lib/axios.ts` for cleaner configuration
-
-### Fixed
-- Fixed race condition in useUserData hook causing stale state (#135)
-- Resolved memory leak when component unmounts during fetch (#133)
-
-### Deprecated
-- `GET /api/v1/users` — use `GET /api/v2/users` instead (removes in v2.0)
-
-### Removed
-- Removed legacy `moment.js` dependency — migrated to `date-fns`
-
-### Security
-- Updated `package-x` from 2.1.0 to 2.1.4 (CVE-2026-XXXX)
-```
-
----
-
-### Phase 5 — Release Notes (Human-Readable)
-
-For non-technical stakeholders:
-
-```markdown
-# Release v1.2.0 — Security & Stability
-
-## What's new
-
-**Better security**: Login sessions are now more secure with automatic
-token rotation. Each time you use the app, your session is refreshed
-automatically.
-
-**More reliable**: The app now automatically retries failed requests,
-so temporary network issues won't interrupt your workflow.
-
-## Bug fixes
-
-- Fixed an issue where user data could appear stale after navigating
-- Fixed a rare crash that occurred when closing the app during data loading
-
-## Under the hood
-
-We've updated several internal libraries to keep the app fast, secure,
-and maintainable.
-```
-
----
-
-## Decision Tree
-
-```
-What does the user need?
-  ├── Commit message     → Phase 2 only
-  ├── PR description     → Phase 3 (+ Phase 2 if commits not written)
-  ├── Changelog entry    → Phase 4 (from commit list or diff)
-  └── Full release       → Phase 2 + Phase 4 + Phase 5
-
-Should changes be split into multiple commits?
-  ├── Changes are unrelated → Yes — split by concern
-  ├── Changes form one atomic feature → No — single commit
-  └── Unsure → Ask user
-
-Is there a breaking change?
-  ├── Yes → Use `feat!` or `fix!` type + BREAKING CHANGE footer
-  └── No  → Standard type
-```
-
----
-
-## Branch Naming Convention
-
-```
-feature/short-description       → new features
-fix/short-description           → bug fixes
-refactor/short-description      → refactoring
-chore/dependency-upgrade        → maintenance
-release/v1.2.0                  → release preparation
-hotfix/critical-issue           → urgent production fixes
-```
-
----
-
-## Output Format
-
-```
-📝 Git Output
-─────────────────────────────────────────────────
-Type:    [commit | PR | changelog | release-notes]
-
-─── Commit Message ───────────────────────────────
-feat(scope): short imperative description
-
-Body explaining why this change was made.
-What problem does it solve?
-
-Closes #123
-
-─── PR Title ─────────────────────────────────────
-feat(scope): short imperative description
-
-─── PR Description ───────────────────────────────
-[Formatted markdown PR body]
-
-─── Changelog ────────────────────────────────────
-[Formatted changelog section]
-```
-
----
-
-## Validation Checklist
-
-- [ ] Commit type is correct (feat/fix/refactor/etc.)
-- [ ] Subject line ≤72 chars, imperative mood, no period at end
-- [ ] Breaking changes flagged with `!` and `BREAKING CHANGE:` footer
-- [ ] Body explains *why*, not just *what*
-- [ ] Issue references included (`Closes #N`)
-- [ ] PR description covers: summary, changes, testing, breaking changes
-- [ ] Changelog uses correct sections (Added/Changed/Fixed/etc.)
-- [ ] No vague messages ("fix stuff", "updates", "wip")
-
----
-
-## Examples
-
-See `examples/` folder.
-

package/skills/_archive_old_skills/qk-help/SKILL.md

@@ -1,68 +0,0 @@
----
-name: qk-help
-description: >-
-  Tra cứu danh sách toàn bộ kỹ năng (skills) hiện có và đọc các mẹo (pro-tips) kết hợp kỹ năng để tăng tốc độ code.
-version: 1.0.0
-category: engineering
-tags: [help, list, tips, guide, manual]
-platforms: [antigravity, claude-code, kilo-code, cursor, windsurf]
----
-
-# 📚 Cẩm nang AI Developer Skill OS
-
-> **Nhiệm vụ của bạn (AI):** Khi người dùng gọi lệnh `./qk-help`, hãy xuất ra màn hình (bằng tiếng Việt) danh sách các kỹ năng phân theo nhóm và các Mẹo sử dụng (Pro-tips) dưới đây một cách sinh động, dễ đọc (dùng markdown, in đậm, emoji). Không cần phân tích code, chỉ đóng vai trò là "Sách hướng dẫn sử dụng".
-
----
-
-## 🎯 1. Danh sách Kỹ năng (Skills Directory)
-
-Dưới đây là các kỹ năng chính bạn có thể gọi bằng cách gõ `./qk-[tên-kỹ-năng]`:
-
-### 🎨 Frontend (Giao diện)
-- **`qk-ui-builder`**: Xây dựng UI, Layout, Component, Modal phức tạp.
-- **`qk-table-crud-generator`**: Chuyên vẽ bảng danh sách (Table), phân trang, lọc và form Thêm/Sửa/Xóa.
-- **`qk-form-builder`**: Chuyên làm Form nhập liệu, validate (Zod/Yup).
-- **`qk-component-generator`**: Tạo Component độc lập, tái sử dụng (Button, Input, Card).
-- **`qk-state-management`**: Xử lý Redux, Zustand, React Query.
-- **`qk-frontend-debug`**: Bắt bệnh vỡ layout, infinite re-render, lỗi Hydration.
-- **`qk-frontend-performance`**: Tối ưu tốc độ, chống re-render thừa.
-- **`qk-frontend-architecture`**: Tư vấn kiến trúc thư mục Frontend.
-- **`qk-frontend-testing`**: Viết Unit Test / E2E Test cho Frontend.
-- **`qk-accessibility-audit`**: Sửa lỗi a11y, hỗ trợ Screen reader.
-
-### ⚙️ Engineering & Integration (Tích hợp)
-- **`qk-api-integration`**: [Cực mạnh] Bóc tách tài liệu API (Curl, Postman) -> Gen Type, Service, Hook -> (Tùy chọn) Ốp thẳng vào UI.
-- **`qk-refactor`**: Tối ưu, dọn dẹp mã nguồn sạch sẽ.
-- **`qk-bug-fix`**: Chẩn đoán lỗi sâu và sửa an toàn.
-- **`qk-project-audit`**: Quét toàn bộ dự án tìm nợ kỹ thuật.
-- **`qk-git-engineer`**: Viết Commit / PR chuẩn Conventional.
-- **`qk-migration`**: Nâng cấp version framework / thư viện.
-- **`qk-agent-orchestrator`**: Kiến trúc sư, lên plan phân rã task lớn.
-- **`qk-context-manager`**: Tóm tắt kiến trúc dự án.
-
-### 🗄️ Backend (Máy chủ)
-- **`qk-database-engineer`**: Thiết kế Schema, ORM (Prisma/Drizzle), Migration.
-- **`qk-backend-architecture`**: Setup kiến trúc Backend (Node/Nest/Python).
-- **`qk-auth-security`**: Phân quyền RBAC, JWT, OAuth.
-- **`qk-deployment`**: Viết Dockerfile, CI/CD Pipeline.
-
----
-
-## 💡 2. Mẹo sử dụng Nâng cao (Pro-Tips)
-
-### Mẹo 1: Kết hợp Kỹ năng (Skill Chaining) 🔗
-Đừng bắt AI làm từ A-Z bằng 1 câu prompt. Hãy gọi liên hoàn:
-> *"Hãy dùng `./qk-api-integration` để bóc tách API này thành hook React Query. Sau đó dùng `./qk-table-crud-generator` vẽ cái Bảng hiển thị danh sách tích hợp hook đó."*
-
-### Mẹo 2: Chế độ "Một phát ăn ngay" (End-to-End) 🚀
-Nếu bạn đã có sẵn 1 màn hình UI (chỉ thiếu data), hãy ép `qk-api-integration` làm End-to-End:
-> *"./qk-api-integration Dưới đây là API Get Profile. Hãy khai báo Type, viết Hook và TÍCH HỢP THẲNG LUÔN vào file \`Profile.tsx\` đang mở."*
-
-### Mẹo 3: Truyền tham số ép buộc (Arguments) 🎯
-Bạn có thể ép AI dùng công nghệ bạn muốn bằng cách thêm \`--tham_số\`:
-> *"./qk-ui-builder --fw=react --css=tailwind Hãy vẽ màn hình Đăng nhập."*
-
-### Mẹo 4: Nhờ "Kiến trúc sư" phân việc 🧠
-Nếu bạn có một tính năng quá lớn (ví dụ: Làm tính năng Giỏ Hàng), đừng tự chia việc, hãy gọi:
-> *"./qk-agent-orchestrator Tôi muốn làm tính năng Giỏ hàng. Hãy phân tích và lên kế hoạch gọi các skill \`qk-\` nào cho phù hợp."*
-

package/skills/_archive_old_skills/qk-migration/SKILL.md

@@ -1,284 +0,0 @@
----
-name: qk-migration
-description: >-
-  Nâng cấp dependency, chuyển đổi framework và thay thế thư viện một cách an toàn với chiến lược không downtime.
-version: 1.0.0
-category: engineering
-tags: [migration, upgrade, dependencies, breaking-change, npm, framework]
-platforms: [antigravity, claude-code, kilo-code, cursor, windsurf]
----
-
-# Migration & Dependency Upgrade
-
-> **Language rule:**
-> Use English for: code, identifiers, file names, architecture terms, technical decisions.
-> Use the user's language for: explanations, questions, summaries, and feedback.
-> The user may write in any language — detect and match it automatically.
-
-> ⚠️ **Always create a rollback plan before starting any migration.**
-> Never apply breaking upgrades to production without a verified fallback.
-
----
-
-## Trigger
-
-Activate this skill when:
-- User wants to upgrade a package or dependency
-- Framework has a new major version (React 17→19, Vue 2→3, Next.js 13→15)
-- A library is deprecated or has a security vulnerability (CVE)
-- User wants to replace one library with another
-- `project-audit` flagged outdated or risky dependencies (P1/P2)
-- User says "update packages", "upgrade to v5", "migrate to new version"
-
----
-
-## Scope
-
-- ✅ Dependency version upgrades (patch, minor, major)
-- ✅ Framework version migrations with breaking changes
-- ✅ Library replacement (swap one library for another)
-- ✅ Package conflict resolution
-- ✅ Configuration updates required by new versions
-- ✅ Code changes required by breaking API changes
-- ✅ Rollback planning
-
----
-
-## Non-goals
-
-- ❌ Do NOT upgrade everything at once — always upgrade incrementally
-- ❌ Do NOT skip reading the changelog/migration guide
-- ❌ Do NOT ignore peer dependency warnings without investigating
-- ❌ Do NOT apply breaking changes without a rollback plan
-- ❌ Do NOT upgrade dev dependencies and prod dependencies in the same step
-
----
-
-## Severity Levels
-
-| Level | Meaning |
-|-------|---------|
-| P0 | Security vulnerability (CVE) — upgrade immediately |
-| P1 | Breaking change affecting core functionality |
-| P2 | Deprecated API with upcoming removal |
-| P3 | Minor version lag — low risk, upgrade when convenient |
-
----
-
-## Migration Types
-
-| Type | Risk | Strategy |
-|------|------|----------|
-| **Patch** (1.0.x → 1.0.y) | Low | Upgrade directly, verify tests |
-| **Minor** (1.x.0 → 1.y.0) | Low-Medium | Read changelog, upgrade, verify |
-| **Major** (x.0.0 → y.0.0) | High | Read migration guide, upgrade incrementally, test thoroughly |
-| **Framework** (React 17→19) | Very High | Follow official migration guide step by step |
-| **Library swap** | High | Strangler fig pattern — migrate incrementally |
-
----
-
-## Workflow
-
-### Phase 1 — Audit Current State
-
-Before upgrading:
-1. List all dependencies with current versions
-2. Identify which are outdated (use `npm outdated` / `pnpm outdated`)
-3. Check for known CVEs (`npm audit` / `pnpm audit`)
-4. Classify each outdated package by migration type and risk
-5. Check peer dependency constraints
-
-```bash
-npm outdated          # See what's outdated
-npm audit             # Security vulnerabilities
-npx depcheck          # Unused dependencies
-```
-
----
-
-### Phase 2 — Read Migration Guide
-
-For every major version upgrade:
-1. Read the official CHANGELOG or migration guide
-2. List all breaking changes that affect the project
-3. List all deprecated APIs still in use
-4. Estimate effort: number of files to change, complexity of changes
-
-Document findings before touching any code.
-
----
-
-### Phase 3 — Plan the Migration
-
-Create an ordered upgrade sequence:
-
-**Rules:**
-- Security fixes first (P0)
-- Dev dependencies before prod dependencies (lower risk)
-- Upgrade one major dependency at a time — not everything together
-- Group related packages (e.g., all `@tanstack/*` together)
-
-**Example order:**
-```
-Step 1: Security patch — package-x 2.1.0 → 2.1.4 (CVE fix)
-Step 2: Dev tools — eslint 8 → 9 (no runtime impact)
-Step 3: Minor upgrades — axios 1.4 → 1.7 (non-breaking)
-Step 4: Major upgrade — react-query 4 → 5 (breaking — separate PR)
-```
-
----
-
-### Phase 4 — Create Rollback Plan
-
-Before applying any change:
-```
-Rollback method:
-  Option A: git revert / git checkout to previous state
-  Option B: Pin version in package.json to previous known-good version
-  Option C: Feature flag to disable new behavior
-
-Rollback trigger:
-  - Tests fail after upgrade
-  - Runtime errors in staging
-  - Performance regression detected
-```
-
----
-
-### Phase 5 — Execute the Upgrade
-
-For each package in the plan:
-
-1. **Upgrade package:**
-```bash
-npm install package-name@version
-# or
-pnpm add package-name@version
-```
-
-2. **Update configuration** (if required by new version)
-
-3. **Fix breaking changes** in code:
-   - Update import paths
-   - Replace deprecated APIs
-   - Update type signatures
-   - Update config files
-
-4. **Run verification** (see Phase 6) before moving to next package
-
----
-
-### Phase 6 — Verify After Each Step
-
-After every upgrade step:
-- [ ] `npm install` / `pnpm install` — no resolution errors
-- [ ] `npm run build` — builds successfully
-- [ ] `npm run type-check` — no new TypeScript errors
-- [ ] `npm run lint` — clean
-- [ ] `npm test` — all tests pass
-- [ ] Manual smoke test of affected features
-
-**If any check fails → rollback this step before continuing.**
-
----
-
-### Phase 7 — Library Replacement (Strangler Fig Pattern)
-
-When replacing one library with another (e.g., moment → date-fns):
-
-```
-Step 1: Install new library alongside old one
-Step 2: Create adapter/wrapper that abstracts the library
-Step 3: Migrate usage file by file (not all at once)
-Step 4: Verify each file after migration
-Step 5: Remove old library when 100% migrated
-Step 6: Remove adapter if no longer needed
-```
-
-This allows incremental migration with rollback possible at any step.
-
----
-
-## Decision Tree
-
-```
-What type of upgrade?
-  ├── Patch/Minor → Upgrade directly, run tests
-  ├── Major       → Read changelog → plan → upgrade → verify
-  └── Framework   → Follow official migration guide step by step
-
-Security vulnerability?
-  ├── P0 (critical) → Upgrade immediately, prioritize over other work
-  └── P1/P2        → Include in next planned upgrade cycle
-
-Library replacement?
-  └── Use strangler fig pattern — never replace all at once
-```
-
----
-
-## Output Format
-
-```
-📦 Migration Report
-─────────────────────────────────────────────────
-Scope:      [What was upgraded / migrated]
-Type:       [Patch / Minor / Major / Framework / Library swap]
-Risk:       [Low / Medium / High]
-
-Changes:
-  ✅ package-x:  2.1.0 → 2.1.4  (CVE fix — no code changes)
-  ✅ axios:      1.4.0 → 1.7.2  (minor — updated interceptor config)
-  ✅ react:      18.2.0 → 19.0.0 (major — updated 12 files)
-
-Breaking changes handled:
-  • [Description of breaking change and how it was resolved]
-
-📋 Rollback plan:
-  git revert <commit-hash> or pin to previous version in package.json
-
-✅ Verification:
-  Build:      PASS
-  Types:      Clean
-  Tests:      PASS (N tests)
-  Lint:       Clean
-  Smoke test: PASS
-
-⚠️  Known issues / follow-up:
-  • [Any remaining deprecated APIs to address]
-  • [Any packages still pending upgrade]
-```
-
----
-
-## Validation Checklist
-
-- [ ] Migration guide read for every major version change
-- [ ] Rollback plan documented before starting
-- [ ] Upgraded incrementally — one major change at a time
-- [ ] `npm audit` clean after upgrade
-- [ ] Build, types, lint, tests all pass
-- [ ] Smoke test of affected features complete
-- [ ] No new peer dependency warnings left unresolved
-- [ ] Breaking changes documented in output
-
----
-
-## Common Migration Cheat Sheet
-
-```
-React 17 → 18:   Concurrent mode, new root API, Suspense updates
-React 18 → 19:   Server components, new hooks (useActionState), ref as prop
-Vue 2 → 3:       Composition API, new reactivity system, breaking changes in lifecycle
-Next.js 12 → 13: App Router introduced (pages/ still works)
-Next.js 13 → 14: Server Actions stable, metadata API
-Next.js 14 → 15: React 19, async params, updated caching defaults
-TanStack Query 4 → 5: New API (no more isLoading/isError split), object syntax
-```
-
----
-
-## Examples
-
-See `examples/` folder.
-