Skill UI

A comprehensive tool designed to help authors assess the suitability and optimal framing of their manuscripts for the IEEE/ACM International Conference on Automated Software Engineering (ASE). It guides the structuring of contributions, required evidence (runnable artifacts, benchmarks), and positioning relative to core SE concepts like program analysis, testing, and AI-assisted development. Use this guide to strategize conference submissions and strengthen the academic narrative.

This skill provides a comprehensive guide for authors determining the fit of their empirical software engineering (SE) manuscript for the International Symposium on Empirical Software Engineering and Measurement (ESEM). It helps authors rigorously check the study design, evidence bar, proper framing, and necessary re-framing required to transform a journal or arXiv-style paper into a high-quality conference submission suitable for ESEM reviewers. It focuses on measurement validity, experimental rigor, and evidence synthesis.

This guide provides comprehensive guidelines for designing, conducting, and auditing empirical studies in software engineering. It emphasizes achieving scientific rigor by matching every claim to specific, measured evidence, ensuring fair baselining (equal budget), and applying appropriate advanced statistics (non-parametric tests, effect sizes). Essential reading for researchers submitting papers based on performance evaluations.

This comprehensive guide is designed for authors submitting revised manuscripts to high-impact journals like the Journal of Software (JOS). It covers the structured approach to responding to reviewers' comments, including point-by-point responses, strategies for handling disagreements, and maintaining consistency across multiple revision rounds. Learn how to professionally transform critical feedback into acceptance.

This comprehensive guide details the mandatory steps for authors preparing a manuscript for final publication in the Journal of Software (JOS). It covers everything from content locking and formatting compliance (2021 template) to meticulous reference checking (GB/T 7714), handling copyrights, and ensuring flawless bilingual consistency between Chinese and English abstracts and keywords. Designed for the critical transition phase between acceptance and final printing.

A comprehensive guide for designing and presenting rigorous experiments for submissions to the Journal of Software (JOS). It guides users through setting clear Research Questions (RQ), selecting real-world datasets and baselines, applying advanced statistical testing (effect size, significance), conducting ablation studies, and addressing threats to validity (internal, external, conceptual). This ensures the evidence strongly supports the claims, meeting top-tier academic standards.

This advanced skill specializes in tracing the complete provenance of software artifacts across the entire development lifecycle. It is designed for deep security analysis of CI/CD pipelines, identifying dependency drift, build tampering, package origin, and determining the final artifact consumed at runtime. Use it when investigating integrity vulnerabilities in complex release flows.

A sophisticated, multi-agent system designed to perform deep, comprehensive code reviews on pull requests. It covers core elements like code quality, functionality, security vulnerabilities, and testing coverage. Advanced features include detecting scope drift, enforcing SOLID principles, identifying DRY violations, and providing anti-hallucination safeguards for maintain high software integrity.

This specialized sub-agent is responsible for transforming high-level feature proposals and technical specifications into a formal, comprehensive 'design.md' document. It systematically captures all necessary technical details, including architectural decisions, data flow diagrams, detailed file changes, API contracts, and thorough testing strategies. Use this skill during the planning phase of any complex software change to ensure technical completeness and feasibility.

This agent is dedicated to systematically exploring technical ideas, such as new features, refactoring, or bug fixes, *before* committing to code changes. It investigates the existing codebase, analyzes current architecture, compares multiple potential approaches (including pros, cons, and effort), and generates a structured 'exploration' report with a clear recommendation and identified risks. It ensures thorough planning and risk mitigation during the design phase.

This sophisticated sub-agent takes comprehensive Software Design Documents (SDD), proposals, and specifications to generate a detailed, actionable task breakdown in the format of a tasks.md file. It structures the work into distinct phases (e.g., Foundation, Core Implementation, Testing, Cleanup), providing concrete, verifiable, and small units of work suitable for immediate engineering execution and managing complex feature delivery chains.

A rigorous framework for triaging software defects, managing technical debt, and designing systemic fixes. This methodology mandates classifying issues by root class and implementing clustered, minimized solutions, rather than applying superficial patches. It guides developers to prevent over-engineering and ensure that system improvements are durable, verifiable, and maintainable.