vcxia

Solid

Use when you need to compare a local or remote repository, extract a feature idea, or prepare an adaptation study without planning or implementing it yet.

AI & Automation 852 stars 197 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 97/100

Stars 20%
98
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Xia Study, compare, and prepare adaptation work from another repository without becoming a second workflow stack. This is a helper skill only. - Do use it for repo-to-repo feature study, comparison, source manifests, dependency mapping, challenge-first trade-off review, and adaptation prep. - Do use it when the user wants to borrow behavior, structure, UX flow, or implementation ideas from another repo and needs a grounded comparison before deciding what to do. - Do not use it to write code, create plans automatically, or bypass the project's planning and execute approval. - Do not use upstream shortcut modes or retired upstream planning/execution command semantics here. ## Approved Modes Only two narrowed modes survive in this kit: - `--compare` - side-by-side analysis only - produce a durable reference or report - `--adapt` - deeper adaptation-prep analysis for the local stack - still stops before planning or implementation Default mode is `--adapt`. ## Core Principles - understand before copy - challenge before plan - adapt, do not transplant - stop before planning or coding ## Workflow ```text [1. Recon] -> [2. Map] -> [3. Analyze] -> [4. Challenge] -> [5. Recommend and Stop] ``` Hard gate: - phase 4 must complete before any implementation recommendation - if the challenge phase exposes major stack or contract drift, downgrade to `--compare` - `xia` never hands off directly to implementation ## Output Policy Default output destination: - durable ...

Details

Author
withkynam
Repository
withkynam/vibecode-pro-max-kit
Created
2 weeks ago
Last Updated
1 weeks ago
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

adaptive-dev-workflow

Workflow router for substantial changes — classify feature / bugfix / refactor / security / perf / OpenSpec into Feature Delivery, Bug Investigation, or Lightweight Maintenance; output required artifacts + gates. Not for tiny edits, investigation already underway, code review, or apply-ready OpenSpec tasks.

1 Updated 1 weeks ago
hmj1026
AI & Automation Solid

ai-explore

Codebase-only read-only research dispatcher. Thin wrapper around the ai-explore agent for architecture mapping, dependency tracing, pattern identification, and risk surfacing. Trigger for 'explore the codebase', 'where does X live', 'map this module', 'what depends on Y', 'trace this import chain'. Not for external evidence with citations; use /ai-research instead.

52 Updated 4 days ago
arcasilesgroup
Code & Development Listed

adk-implement

Implement, build, add, write, ship, code-up, wire-up code in an existing repo. Triggers on: Jira URL or KEY-NUM (specialized from-jira sub-flow — the most common path), GitHub issue URL or #N (from-issue), Confluence TDD URL (from-tdd), Slack thread permalink (from-slack-thread), or a freeform description (greenfield). Git mandatory; GitHub MCP optional but enables PR-by-URL flow. Every run: question-first (3 questions max), advisor-strategy plan with 2–4 trade-off options, edit-format discipline (SEARCH/REPLACE blocks per shared/edit-format.md), repo-native typecheck+lint+narrow-tests on each checkpoint. Writes plan/steps/diffs/report under `<repo>/.temp/adk/implement/<task>/`. Pushes only after explicit confirmation; never force-pushes; never merges; never touches a protected branch. Pulls Jira context via adk-mcp-atlassian, GitHub context via adk-mcp-github, and optional RAG via adk-mcp-rag. Supports --plan (read-only planning) → --act (writes). Sub-flows under references/.

0 Updated 1 weeks ago
sujeet-pro