Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
A skill your agent uses when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring…
Install Icsme Topic Selection
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-topic-selection --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ICSME-Skills/skills/icsme-topic-selection .claude/skills/icsme-topic-selection && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "icsme-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selection into .claude/skills/icsme-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-topic-selection", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selectionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-topic-selection --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ICSME-Skills/skills/icsme-topic-selection .agents/skills/icsme-topic-selection && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "icsme-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selection into .agents/skills/icsme-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-topic-selection", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-topic-selection --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ICSME-Skills/skills/icsme-topic-selection .cursor/skills/icsme-topic-selection && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "icsme-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selection into .cursor/skills/icsme-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-topic-selection", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ICSME-Skills/skills/icsme-topic-selection--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-topic-selection --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ICSME-Skills/skills/icsme-topic-selection .gemini/skills/icsme-topic-selection && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "icsme-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selection into .gemini/skills/icsme-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-topic-selection", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-topic-selectionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ICSME-Skills/skills/icsme-topic-selection .github/skills/icsme-topic-selection && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "icsme-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selection into .github/skills/icsme-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-topic-selection", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-topic-selection --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ICSME-Skills/skills/icsme-topic-selection .opencode/skills/icsme-topic-selection && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "icsme-topic-selection" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-topic-selection into .opencode/skills/icsme-topic-selection/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-topic-selection", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
icsme-topic-selection- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 625 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring…
- Deciding whether a software-engineering project belongs at IEEE ICSME (maintenance
- SKILL.md covers The routing question that…, Sibling-venue routing table, Contribution shapes ICSME… and The re-label and lifecycle tests, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Reverse engineering
What it does
Icsme Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring, mining software repositories) or should be routed to ICSE, FSE, ASE, ISSTA, MSR, SANER, SCAM, or an SE journal (TSE/EMSE), and when to use ICSME's Journal-First, Registered Reports, or RENE tracks instead of the research track.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Technical debt, Reverse engineering and malware and Refactoring. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Deciding whether a software-engineering project belongs at IEEE ICSME (maintenance
- Reverse engineering
- Program comprehension
- Mining software repositories)
Example prompts
- “/icsme-topic-selection”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Icsme Topic Selection loads about 1.7k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 625 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 625 words, ~1,679 tokens.
Download SKILL.mdSave it as
.claude/skills/icsme-topic-selection/SKILL.md (or your agent's skills folder).- name
- icsme-topic-selection
- description
- Use when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring, mining software repositories) or should be routed to ICSE, FSE, ASE, ISSTA, MSR, SANER, SCAM, or an SE journal (TSE/EMSE), and when to use ICSME's Journal-First, Registered Reports, or RENE tracks instead of the research track.
ICSME Topic Selection
Decide the venue before drafting. ICSME — the IEEE International Conference on Software Maintenance and Evolution — is the field's dedicated home for what happens to software after the first release: maintaining it, evolving it, comprehending it, refactoring it, repaying its technical debt, and mining the repositories that record its history. A brilliant paper about a greenfield synthesis technique, a novel type system, or a pure ML model is respected and then rejected as out of scope. The ICSME question is not "is this good SE?" but "is the paper's centre of gravity a real maintenance-or-evolution problem?"
The routing question that matters most
ICSME overlaps ICSE and FSE (both take maintenance work) and SANER, SCAM, MSR, and ICPC (all maintenance-adjacent). The decisive test is which community the paper is arguing with and how central the maintenance lifecycle is to the contribution — plus which live deadline fits. A paper whose evidence is a legacy system aging under change, a refactoring that developers must trust, or a bug that survived years of evolution is natively ICSME; a paper that only uses software as a substrate for a general technique usually belongs elsewhere.
Sibling-venue routing table
| Signal in your project | Better home | Why |
|---|---|---|
| Maintenance/evolution problem is the heart: aging systems, change impact, technical debt, refactoring safety, program comprehension | ICSME | The venue built for the post-release lifecycle |
| Broad SE technique or study aimed at the whole field, not specifically maintenance | ICSE / ESEC/FSE | General-SE flagships with wider scope and a larger stage |
| The whole method is repository mining and the research question is about mining itself | MSR | Purpose-built mining venue (ICSME takes mining applied to maintenance) |
| Static/dynamic source-code analysis or transformation is the core machinery | SCAM | Co-located with ICSME; deeper source-analysis expertise |
| Reverse engineering / comprehension with a strong tooling or human angle, early-stage | SANER / ICPC | Evolution-adjacent siblings with their own communities |
| Testing depth or fault detection is the contribution | ISSTA / ASE | Testing/analysis and automation venues |
| Study too long or too deep for the 10-page IEEE budget | TSE / EMSE | Journals with no conference ceiling — and the door back via ICSME's Journal-First track |
Show full SKILL.md (278 more words)Show less
Contribution shapes ICSME rewards
- Maintenance/evolution technique + tool + evaluation on real, evolving systems — a change- impact, refactoring, migration, comprehension, or debt-detection technique, embodied in a tool and evaluated on real systems with real change history.
- Empirical study of how software ages and changes — mining commit, issue, PR, or release history to characterize maintenance practice, defect survival, debt accumulation, or evolution.
- Reverse engineering / program comprehension — recovering architecture, models, or intent from existing code, with evidence it helps a maintainer.
- Replication or negative result (the RENE track's home turf) — re-running prior maintenance research on new data and reporting honestly what did and did not reproduce.
- Technical-debt and refactoring economics — measuring, predicting, or repaying debt, or demonstrating that a refactoring preserves behaviour and pays off.
The re-label and lifecycle tests
Two quick tests sharpen a borderline verdict:
- Lifecycle test: does the contribution only make sense because software already exists and keeps changing? If you can restate it with no reference to history, maintenance, or evolution, ICSME is probably the wrong room — route to ICSE/FSE or a technique venue.
- Re-label test: could this be submitted to MSR or SCAM unchanged and read as native there? If its heart is mining-for-its-own-sake or source transformation machinery, route accordingly; ICSME rewards the maintenance payoff of that machinery, not the machinery alone.
Choosing an ICSME track (not just the research track)
ICSME is unusual in how many doors it opens — pick the one that fits the work's maturity:
[Research track] a complete maintenance/evolution technique or study, ready now
[Journal-First (J1C2)] a TSE/EMSE paper already accepted (2025-2026 window) not yet conf-presented
[Registered Reports] a strong protocol whose result is not yet in -> lock the method, review-first
[RENE] a replication/reproduction on new data, or an honest negative result
[NIER / Visions] an early idea with an argument but not a full study
[Tool Demo / Data] a usable tool or a released dataset as the contribution
[Industry] a practitioner-driven maintenance experience reportCheap reconnaissance before committing
[Scope] scan the last two ICSME programs (dblp conf/icsm, conf.researchr.org) for your subarea
-> 3+ recent papers = a reviewer pool exists; 0 = opening or mismatch
[Citations] is your bibliography majority maintenance/evolution venues (ICSME/SANER/MSR/ICPC/TSE/EMSE)?
-> majority elsewhere => reviewers read you as a visitor; ground the intro in maintenance first
[Calendar] compare the next ICSME abstract deadline with ICSE/FSE/SANER/journal dates -> route to the
nearest honest fit rather than idling a yearDecision procedure
[Audience] who acts differently if the claim holds? -> maintainers/reverse-engineers/evolution researchers?
[Claim type] technique / empirical / comprehension / replication / debt-economics
[Lifecycle check] does it depend on software already existing and changing? -> yes = ICSME-shaped
[Sibling check] mining-only -> MSR; source transformation -> SCAM; general SE -> ICSE/FSE
[Track choice] research / journal-first / registered report / RENE / NIER / tool-demo / industry
[Verdict] ICSME <track> / sibling venue / journal-first, with a one-line reasonRun this before the writing skills; a wrong venue or wrong-track decision wastes every later step.
When the verdict is ICSME, continue with icsme-workflow for the calendar and
icsme-writing-style for the paper shape.
© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ICSME-Skills/skills/icsme-topic-selection of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icsme Topic Selection next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Icsme Topic Selection this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT | |
| Code Simplification for ego-litecitrolabs/ego-lite | 17k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Code Refactoring Workflowluongnv89/claude-howto | 42k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Tech Debt Analyzerailabs-393/ai-labs-claude-skills | 454 | 2 repos | ~3.9k | Automated safety check: Pass | MIT | |
| FIXME Resolvertailcallhq/forgecode | 7.6k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Code Simplification for ego-lite
citrolabs/ego-lite
Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.
Code Refactoring Workflow
luongnv89/claude-howto
Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.
Tech Debt Analyzer
ailabs-393/ai-labs-claude-skills
This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability.
FIXME Resolver
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
Desloppify
Git-on-my-level/codex-autorunner
Codebase health scanner and technical debt tracker. An agent skill from Git-on-my-level/codex-autorunner.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Icsme Topic Selection
What does Icsme Topic Selection do?
A skill your agent uses when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring…. Icsme Topic Selection is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding whether a software-engineering project belongs at IEEE ICSME (maintenance, evolution, reverse engineering, program comprehension, technical debt, refactoring, mining software repositories) or should be routed to ICSE, FSE, ASE, ISSTA, MSR, SANER, SCAM, or an SE journal (TSE/EMSE), and when to use ICSME's Journal-First, Registered Reports, or RENE tracks instead of the research track.
When should I use Icsme Topic Selection?
Icsme Topic Selection fits situations like: deciding whether a software-engineering project belongs at IEEE ICSME (maintenance; reverse engineering; program comprehension; mining software repositories).
How do I install Icsme Topic Selection in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a claude-code`. Or copy the skill folder (ICSME-Skills/skills/icsme-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icsme-topic-selection in your project. Claude Code loads it when a task matches its description.
How do I install Icsme Topic Selection in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a codex`. Or copy the skill folder (ICSME-Skills/skills/icsme-topic-selection in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icsme-topic-selection in your project. Codex loads it when a task matches its description.
Can I use Icsme Topic Selection in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-topic-selection -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/icsme-topic-selection, .gemini/skills/icsme-topic-selection, .github/skills/icsme-topic-selection and .opencode/skills/icsme-topic-selection in your project.
What does Icsme Topic Selection need to run?
SKILL.md names no scripts, command-line tools or credentials: Icsme Topic Selection is instructions for the agent only.
Does Icsme Topic Selection access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Icsme Topic Selection safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Icsme Topic Selection use?
Icsme Topic Selection is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Icsme Topic Selection use?
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icsme Topic Selection?
Skills that share tags, products or a category with Icsme Topic Selection: Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Code Simplification for ego-lite (citrolabs/ego-lite, 17k stars), Code Refactoring Workflow (luongnv89/claude-howto, 42k stars) and Tech Debt Analyzer (ailabs-393/ai-labs-claude-skills, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icsme Topic Selection?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.