Individual skill

icsme-experiments

Use when designing or auditing IEEE ICSME empirical evaluations, covering real evolving subject systems, mining-software-repositories provenance, fair baselines, SE-standard statistics and effect sizes, change-history and survivorship confounds, qualitative rigor, contamination-aware LLM ablations, and matching evidence to the shape of each maintenance/evolution claim.

ICSME-Skills/skills/icsme-experiments/SKILL.md

Read pinned source

Source commit 932eb23331721b16e967c59f093781be1928b498

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,404
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# ICSME Experiments

Use this before submission when the empirical story is not yet locked. ICSME reviewers are
maintenance and evolution empiricists, and because the venue has **no revision round**, the
evaluation must be complete on submission — you cannot promise a missing analysis and add it later.
The organizing principle is **evidence proportional to the claim**, tested on **real systems with
real change history**, not on synthetic snapshots.

## Evaluation audit

- **Match evidence to the claim shape.** A claim about *maintenance effort* needs effort or proxy
  data defended as a proxy; a claim about *change impact* needs real change sets; a claim about
  *comprehension* needs a human study; a claim about *debt* needs a debt measurement, not lines of
  code. Accuracy against a convenient label is not evidence for a maintenance-practice claim.
Back to top