agentleFS
Sign inStart free
AWSKnown publisherawslabs/amazon-dynamodb-tools/tools/bulk_executor/.claude/CLAUDE.md

amazon-dynamodb-tools / bulk_executor

CLAUDE.md182 starsChanged 5 months agoApache-2.0View on GitHub

After completing a logical set of changes, run the unit tests to verify nothing is broken. All python commands must activate the local virtual environment first. From the tools/bulk_executor/ directory:

The file

We split this CLAUDE.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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:

    After completing a logical set of changes, run the unit tests to verify nothing is broken.

    line 5
  2. Distinctive:

    All python commands must activate the local virtual environment first.

    line 7
  3. Distinctive:

    After completing a cohesive set of related changes (not after every single edit)

    line 19
  4. Distinctive:

    Before reporting that a task is complete

    line 20
  5. Distinctive:

    After refactoring or modifying existing functionality

    line 21
  6. Very specific:

    Use make test-client or make test-server if changes are scoped to only one side

    line 25
  7. Distinctive:

    If tests fail, fix the issues before moving on

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

Skills

Run Unit Tests

After completing a logical set of changes, run the unit tests to verify nothing is broken.

All python commands must activate the local virtual environment first.

Steps

From the tools/bulk_executor/ directory:

source .venv/bin/activate && make install && make test

When to run

  • After completing a cohesive set of related changes (not after every single edit)
  • Before reporting that a task is complete
  • After refactoring or modifying existing functionality

Notes

  • Use make test-client or make test-server if changes are scoped to only one side
  • If tests fail, fix the issues before moving on

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.

Check your setup, free