Skill UI

This guide details the rigorous and multi-stage academic review process for submissions to the PODS conference. It moves beyond simple accept/reject decisions, explaining the importance of multi-cycle revisions, shepherded rounds, and the strict focus on mathematical proofs and theoretical correctness. It helps authors understand how to strategically strengthen their work for high-impact, theory-based venues.

This guide details the complete academic lifecycle for a paper submitted to the POPL conference, culminating in a journal issue. It covers all critical stages: double-blind review, handling author responses, navigating conditional acceptance, mandatory revisions, and understanding how academic rigor (correctness, novelty, significance) is assessed by the committee. Essential reading for researchers.

This comprehensive guide outlines the rigorous methodology required for designing high-impact evaluations of parallel systems and algorithms for top-tier conferences. It stresses that contributions must demonstrate the 'twin bar': both concurrency correctness (e.g., linearizability) and measurable scalability (e.g., strong vs. weak scaling). It covers best practices for establishing strong baselines, managing measurement hygiene (variance, pinning), and anticipating advanced reviewer scrutiny in HPC.

A comprehensive deep dive into the PPoPP conference review pipeline. This guide models the single-round, double-blind review process, detailing how submissions are evaluated by the Program Committee and External Review Committee. It covers critical aspects such as the author response rebuttal, automatic poster consideration, and the specific technical axes reviewers prioritize (e.g., scalability, concurrency correctness, baseline honesty) for parallel programming research.

This guide helps researchers structure their academic papers for the PPoPP conference. It outlines the principle of 'decision-criticality,' advising authors to keep core correctness arguments, headline scaling curves, and design insights in the main body, while moving bulk data, full proofs, and extensive sweeps to the artifact or appendix.

A comprehensive guide detailing the rigorous standards required for submitting parallel programming research to top-tier academic venues. It covers crucial topics such as proving concurrency correctness, demonstrating measurable scalability using speedup curves, adhering to strict formatting (10 pages, two-column layout), and structuring the technical contribution to satisfy expert reviewers.

This guide outlines best practices for PRL submissions, detailing how to select suggested and opposed referees. It emphasizes demonstrating both scientific correctness and broad interdisciplinary significance to preempt likely reviewer objections, maximizing the letter's chance of acceptance.

A comprehensive model detailing the rigorous evaluation process for submissions to STOC (Symposium on Theory of Computing). It covers the committee structure, the roles of program committee members and external subreviewers, the key evaluation axes (Correctness, Significance, Breadth, Novelty), the typical timeline, and strategic advice for authors on maximizing their leverage throughout the double-blind review process.

This guide provides a strategic framework for drafting author responses to challenging peer reviews in academic conferences. It teaches authors how to structure replies by addressing four key axes (Correctness, Novelty, Backing, Clarity), ensuring technical precision, maintaining anonymity, and framing commitments that survive the subsequent Area Chair (AC) discussion phase.

This tool provides a preferred, end-to-end method for modifying code in real-world repositories. It simulates a professional development workflow: cloning the target repository, running changes on a dedicated task branch, and critically, verifying the implementation through an independent red $\to$ green $\to$ regression test loop. It is designed for fixing GitHub issues, implementing new features, or adding functions to existing codebases, ensuring the structural integrity and correctness of the changes.

An advanced tool designed to audit, validate, and maintain rule files (e.g., .claude/rules/). It checks structural correctness, validates glob patterns against actual project files, and runs an interactive session to confirm or improve the relevance of each rule. Ideal for initial setup, debugging, or periodic rule hygiene.

This tool leverages an LLM-as-a-Judge agent to thoroughly evaluate staged Git changes before they are committed. It checks for correctness, completeness, and safety issues, providing a detailed verdict (APPROVE, NEEDS_REVIEW, REJECT) and actionable feedback. It is essential for maintaining high code quality, especially in complex or security-sensitive code sections.