agentleFS
ronedgecombronedgecomb/anything/skills/no-tombstones/SKILL.md

no-tombstones

Skill1 starsChanged 9 days agoApache-2.0View on GitHub

Keep code, tests, comments, and documentation focused on current requirements. Use during ordinary creation, modification, review, and cleanup to prevent unnecessary residue of previous implementations. Retain historical references and absence checks when they protect a concrete ongoing need.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Document current behavior and test current requirements.

    line 9
  2. Distinctive:

    Keep comments that explain non-obvious behavior, reasons, and trade-offs.

    line 17
  3. Distinctive:

    Use the appropriate existing place for needed migration guidance or decision history.

    line 18
  4. Distinctive:

    Prefer tests of supported public behavior and current requirements.

    line 22
  5. Distinctive:

    Avoid permanent tests whose only purpose is proving that a removed filename, symbol, string, or implementation is absent.

    line 23
  6. Very specific:

    Keep an absence check when absence itself protects a concrete current contract.

    line 24
  7. Distinctive:

    When replacing a tombstone test, preserve any meaningful behavior it also covers.

    line 27
  8. Distinctive:

    Remove affected commented-out implementations, obsolete branches, and placeholder wrappers when their lack of a current consumer or …

    line 31
  9. Distinctive:

    Keep the resulting code coherent.

    line 33
  10. Distinctive:

    Remove or rewrite material with no ongoing purpose, preserving useful coverage and required guidance.

    line 53

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

No tombstones

Document current behavior and test current requirements. A tombstone is material left behind or newly added mainly to describe or forbid a previous implementation, without serving a concrete ongoing purpose.

Apply this guidance during ordinary work within the requested scope. Respect review-only requests and preserve unrelated work. Existing tombstones can be addressed during an authorized review or cleanup; finding one does not expand the task.

Documentation and comments

  • Explain the current architecture, supported usage, and constraints directly. Replace affected stale explanations with accurate ones.
  • Omit sentences whose only purpose is announcing that an old approach was removed, such as "This no longer uses the old parser." Keep a historical comparison when the reader needs it to act or understand a current constraint.
  • Keep comments that explain non-obvious behavior, reasons, and trade-offs. Remove affected comments that merely mark where deleted functionality used to be.
  • Use the appropriate existing place for needed migration guidance or decision history. Change summaries and requested historical accounts can describe transitions. Do not create a history document just to preserve removed material.

Tests and verification

  • Prefer tests of supported public behavior and current requirements. Keep meaningful regression coverage, including tests motivated by an old bug; name and assert the behavior they protect.
  • Avoid permanent tests whose only purpose is proving that a removed filename, symbol, string, or implementation is absent. Removal alone does not establish a requirement for a new absence test.
  • Keep an absence check when absence itself protects a concrete current contract. For example, an explicitly retired endpoint may be required to return 410 Gone; test that observable response through its public interface.
  • Establish the ongoing requirement from the request, project policy, supported contract, or other evidence. Speculation that an old implementation might return is insufficient justification.
  • Temporary searches and diff inspection can verify a requested removal without becoming permanent tests. Match lasting coverage to the behavior that must continue to hold.
  • When replacing a tombstone test, preserve any meaningful behavior it also covers. An assertion's negative form alone does not make it a tombstone.

Code

Remove affected commented-out implementations, obsolete branches, and placeholder wrappers when their lack of a current consumer or requirement is established. Preserve required compatibility and verify consumers before removing an interface or shim.

Keep the resulting code coherent. Avoid leaving empty structures, misleading names, or explanatory remnants solely to mark the previous design.

Keep history with a current purpose

Migration instructions, supported compatibility, operational constraints, decision rationale, and explicitly requested history can justify references to previous implementations. Identify the real purpose and keep the material proportionate. Apply established requirements without a new approval ritual; clarify only consequential uncertainty or conflicts.

Examples:

SituationUseful result
A storage implementation is replacedDocument current setup and usage; remove the affected stale instructions.
A private helper is deletedExercise the supported behavior and inspect remaining references during the change.
A bug is fixedKeep a regression test for the required behavior.
A retired endpoint is required to return 410 GoneTest that response through the public interface.
Users must migrate a supported older configurationKeep the instructions needed for that migration in an appropriate existing location.

Check the result

For each affected explanation, comment, or assertion, identify the current requirement or reader need it serves. Someone unfamiliar with the previous implementation should be able to understand why ordinary documentation and tests exist.

Remove or rewrite material with no ongoing purpose, preserving useful coverage and required guidance. Verify the affected behavior, links, and references as appropriate. Report actual changes and checks in the task's normal completion summary; a separate report is optional.

Download now (ZIP)

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.