Individual skill

icsme-writing-style

Use when revising an IEEE ICSME paper for a maintenance/evolution contribution stated on the first page, research-question contracts, a threats-to-validity section that argues rather than recites, evidence proportional to the claim, double-anonymous wording, and disciplined use of the IEEEtran two-column 10-page budget.

ICSME-Skills/skills/icsme-writing-style/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: Yes
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.

academic-writing Repository topic
agent-skills Repository topic
journal Repository topic
academic-research Repository topic
ai-agents Repository topic
anthropic Repository topic
awesome-list Repository topic
claude Repository topic
claude-code Repository topic
economics Repository topic
research Derived category
finance Derived category
writing Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 5,458 bytes

Read excerpt


# ICSME Writing Style

Use this when revising the main paper. ICSME papers are read by maintenance and evolution
empiricists, so they need a **software-maintenance contribution stated on the first page** and
evidence a reviewer trusts. The failure this skill prevents is a technically fine paper that reads
like a greenfield systems demo or a generic ML result with a maintenance title glued on — the
`icsme-topic-selection` re-route signal.

## Revision rules

- **Lead with the maintenance/evolution problem:** the situation a maintainer recognizes (a system
  aging under change, debt accruing, a refactoring nobody trusts, comprehension lost over years),
  why the current state is inadequate, the contribution, the evidence, and what changes for people
  who maintain software.