To Run or Not to Run
Analyzes the cost and benefit of code execution in LLM-based repair, arguing that execution feedback is a costly resource rather than a default action.
I am a Ph.D. student at Beihang University, working in the SMAT Laboratory under Prof. Li Li, co-supervised by Mingyi Zhou.
My research focuses on AI for Software Engineering (AI4SE), combining large language models, program analysis, and verifiable software-engineering environments to build reliable coding agents and ecosystem toolchains. The work spans execution feedback, repository-scale benchmarks, change impact analysis, OpenHarmony quality assurance, and low-resource programming languages — all around one core question: how to make AI genuinely reliable for software engineering practice.
LLMs already generate code well, but real software engineering is not only about writing a patch: an agent must understand repositories, select evidence, control execution cost, maintain change history, and survive verification in a specific ecosystem. My central question is how to combine LLM generation, the determinism of program analysis, and real software-engineering environments into reliable coding agents and ecosystem toolchains.
In coding agents, this means analyzing when execution feedback is worth its cost (To Run or Not to Run) and using lightweight static structure to stabilize repository navigation (CodeAnchor). In the OpenHarmony ecosystem, it means combining domain rules, static analysis, LLMs, and real feedback for repair, migration, and performance analysis (HapRepair, Phantom Rendering Detection). On the evaluation side, it means systematically examining what code knowledge LLMs actually understand and how AI4SE tools should be measured.
Analyzes the cost and benefit of code execution in LLM-based repair, arguing that execution feedback is a costly resource rather than a default action.
Studies how lightweight static structure acts as deterministic anchors, improving localization stability, reproducibility, and navigation efficiency in real repositories.
Identifies unnecessary UI computations so developers can find hidden performance bottlenecks and improve mobile app smoothness.
Proposes a multi-agent reinforcement learning framework that dynamically evaluates jailbreak vulnerabilities in LLM safety defenses.
Four threads sharing one question: how to make coding agents both reliable and verifiable in real software-engineering environments. Click to expand.
Performance analysis tool for OpenHarmony apps, detecting Phantom Rendering issues in UI.
FSE 2026 · GitCode
Static checker and auto-repair tool for OpenHarmony apps; core module of HapRepair.
FSE Industry 2025 · GitCode
Android → OpenHarmony migration tool, helping apps enter the HarmonyOS ecosystem.
Migration tool · GitCode
AI-powered research desktop app: literature management, smart reading notes, and idea generation.
Electron + TypeScript · GitHub
SKILL coverage and optimization framework for Codex / Claude Code agent traces.
Agent Skills · GitHub
OpenHarmony / mobile app quality
Topics: OpenHarmony app repair, Phantom Rendering / UI performance analysis, Cangjie low-resource language fine-tuning
LLM code understanding / AI4SE evaluation
Heartfelt thanks to Wei Ma for guiding me into research. When I first began, he patiently helped me with topic selection, paper reading, experiment design, and writing; much of my early research training was shaped by his guidance and support.
Topics: LLM code understanding and semantic evaluation, MazeBreaker adaptive evaluation, AI4SE open-source ecosystem studies
LLM agents / execution efficiency
Heartfelt thanks also to Zhensu Sun. After I became able to develop research ideas more independently, he continued to offer constructive advice on problem framing, experiment design, paper narrative, and limitation analysis, helping me learn how to refine early ideas into more complete and solid research work.
Topics: LLM coding agents, Execution cost and latency optimization, Code generation and repair evaluation