agentleFS
adobeadobe/S3Mock/.agents/skills/refactor/SKILL.md

refactor

Skill1.2k starsChanged 3 months agoApache-2.0View on GitHub

Improve code readability, enforce idiomatic Kotlin conventions, and enhance documentation quality in S3Mock without changing behavior. Use when asked to clean up code, improve naming, add KDoc, or align with Kotlin/project idioms. Also invoked by the implement and test skills before adding new code to messy areas.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 160 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use to clean up code structure/naming, improve or add KDoc, remove anti-patterns, or prepare code before a feature addition (invoked by the …

    line 10
  2. Very specific:

    Hard constraint: must not change observable behavior.

    line 12
  3. Distinctive:

    Read root AGENTS.md and the relevant module AGENTS.md.

    line 16
  4. Distinctive:

    Read callers and tests to understand the code's purpose before making any changes.

    line 17
  5. Very specific:

    Run make test and/or make integration-tests to verify no behavior changed.

    line 23
  6. Very specific:

    Update the copyright year in every modified file (INVARIANTS.md).

    line 24

“Common” is measured: kept by at least 6 in 10 of the 160 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Refactor Skill

Entry Criteria

Use to clean up code structure/naming, improve or add KDoc, remove anti-patterns, or prepare code before a feature addition (invoked by the implement/test skill).

Hard constraint: must not change observable behavior. If a change would alter behavior, it belongs in the implement skill instead.

Before Starting

  1. Read root AGENTS.md and the relevant module AGENTS.md.
  2. Read callers and tests to understand the code's purpose before making any changes.
  3. Confirm existing test coverage is sufficient to catch regressions.

Execution Steps

  1. Apply naming, comment, KDoc, and idiom fixes per docs/KOTLIN.md.
  2. Run make test and/or make integration-tests to verify no behavior changed.
  3. Update the copyright year in every modified file (INVARIANTS.md).
  4. Invoke the lint skill.

Completion Criteria

  • No behavior changes — tests still pass
  • Follows docs/KOTLIN.md naming, comment, and idiom conventions
  • Copyright year updated in every modified file
  • Lint gates pass (via lint skill)

Resources

  • AGENTS.md, INVARIANTS.md
  • Relevant module AGENTS.md
  • docs/KOTLIN.md

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 1 mentionJan 2026: 2 mentionsFeb 2026: 2 mentionsMar 2026: 1 mentionApr 2026: 3 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 1 mentionOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the adobe/S3Mock repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about adobe/S3Mock

The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 50

Talked about on GitHub, Stack Overflow and Hacker News (50 times).

On GitHub · 46

41 more on GitHub

On Hacker News · 1

  • Other versions187 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 187

    1. github/awesome-copilot★ 41ksame name
    2. unkeyed/unkey★ 5.5ksame name
    3. parcadei/Continuous-Claude★ 3.9ksame name
    4. parcadei/Continuous-Claude-v2★ 3.9ksame name
    5. parcadei/Continuous-Claude-v3★ 3.9ksame name
    6. SethGammon/Citadel★ 927same name
    7. poshan0126/dotclaude★ 871same name
    8. JordanCoin/codemap★ 707same name
    9. membrane/api-gateway★ 656same name
    10. Trevoke/org-gtd.el★ 485same name

    177 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use debug-fix, ascii-diagram and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • zebbernSkill

      debug-fix

      Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)

      Also in 4 projects that use this

    • SethGammonSkill

      ascii-diagram

      Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

      Also in 4 projects that use this

    • parcadeiSkill

      agent-context-isolation

      Agent Context Isolation

      Also in 3 projects that use this

    • parcadeiSkill

      agentica-infrastructure

      Reference guide for Agentica multi-agent infrastructure APIs

      Also in 3 projects that use this

    • +8 more from parcadei
  • In this repository10 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.