researcher
Researcher Skill
Sharded deep research for large repositories using the Qianji runtime (xiuxian-qianji) and a suspend/resume approval loop.
Architecture
┌─────────────┐ ┌────────────────┐ ┌──────────────────┐
│ Setup │ --> │ Architect Plan │ --> │ Await Approval │
│ clone + map │ │ shard proposal │ │ suspend/resume │
└─────────────┘ └────────────────┘ └──────────────────┘
│
▼
┌──────────────────┐
│ Deep Analysis │
│ approved shards │
└──────────────────┘
Command
git_repo_analyer
Core command to execute repository research via Qianji.
Parameters:
repo_url(string, required): Git repository URL to analyze.request(string, optional): Research goal. Default:"Analyze the architecture".action(string, optional):"start"or"approve". Default:"start".session_id(string, required forapprove): Session returned bystart.approved_shards(string, required forapprove): Approved plan JSON string.
Execution model:
action="start":- clones and maps repository,
- asks architect to propose shard plan,
- returns
session_id,proposed_plan, and approval prompt.
action="approve":- resumes same session with approved shard JSON,
- runs deep analysis for approved shards,
- returns final analysis payload.
Output
The command returns structured JSON. Typical fields:
successsession_idmessage/proposed_plan(start phase)analysis_result/full_context(approve phase)
Implementation Notes
- Runtime backend is
xiuxian-qianji(Rust). - Python entrypoint is
scripts/research_entry.py. - Utility functions for clone/map/compress/save are in
scripts/research.py. - Workflow definition is
workflows/repo_analyzer.toml.
Files
researcher/
├── SKILL.md
├── README.md
├── scripts/
│ ├── research.py
│ └── research_entry.py
├── workflows/
│ └── repo_analyzer.toml
└── tests/
More from tao3k/omni-dev-fusion
crawl4ai
Use when crawling web pages, extracting markdown content, or scraping website data with intelligent chunking and skeleton planning. Use when the user provides a URL or link to fetch or crawl.
50software_engineering
Use when analyzing project architecture, exploring codebase structure, understanding system design, reviewing code patterns, or navigating modular components.
18python_engineering
Use when linting Python code, formatting with ruff/black, running pytest tests, type checking with pyright, or modernizing Python 3.12+ standards.
18code_tools
Use when searching code by structure or meaning, analyzing code patterns, finding class or function definitions, or exploring codebase architecture.
16rust_engineering
Use when analyzing Rust project structure, managing Cargo dependencies, building and testing Rust projects, or generating Rust code.
16git
Use when committing code, managing branches, pushing to remote, creating pull requests, or performing version control operations. Conforms to docs/reference/skill-routing-value-standard.md.
15