agentleFS
apacheapache/streampipes/streampipes-service-core/AGENTS.md

streampipes / streampipes-service-core

AGENTS.md756 starsChanged 52 days agoApache-2.0View on GitHub

Applies to streampipes-service-core/. Root AGENTS.md applies as well; build and validation commands live there. - Backend entrypoint and runtime wiring (StreamPipesCoreApplication). - Security setup: WebSecurityConfig, the token filter, OAuth handlers. The list of unauthenticated endpoints is UnauthenticatedInterfaces, applied by WebSecurityConfig. - Startup tasks, migrations and schedulers. Orchestration only — domain behaviour belongs in the *-management modules. 1. Create the class under migrations/v<release>/ (for example migrations/v099/) implementing migrations.Migration: shouldExecute(), executeMigration(), getDescription(). 2. shouldExecute() must make the migration idempotent — it runs…

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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. Very specific:

    Create the class under migrations/v<release>/ (for example migrations/v099/) implementing migrations.Migration: shouldExecute(), …

    line 24
  2. Distinctive:

    Treat partial failure explicitly — log and rethrow rather than leaving a half-migrated state silently.

    line 34
  3. Distinctive:

    Do not put long-running or blocking work on startup thread paths.

    line 40

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

AGENTS Guide (Service Core)

Scope

Applies to streampipes-service-core/. Root AGENTS.md applies as well; build and validation commands live there.

Module intent

  • Backend entrypoint and runtime wiring (StreamPipesCoreApplication).
  • Security setup: WebSecurityConfig, the token filter, OAuth handlers. The list of unauthenticated endpoints is UnauthenticatedInterfaces, applied by WebSecurityConfig.
  • Startup tasks, migrations and schedulers. Orchestration only — domain behaviour belongs in the *-management modules.

High-risk areas

  • Authentication flow and the unauthenticated-endpoint list.
  • Migration registration and execution (migrations/AvailableMigrations, MigrationsHandler).
  • Scheduled side effects (data lake retention, certificate jobs).

Recipe: add a migration

  1. Create the class under migrations/v<release>/ (for example migrations/v099/) implementing migrations.Migration: shouldExecute(), executeMigration(), getDescription().
  2. shouldExecute() must make the migration idempotent — it runs on every start. Detect the already-migrated state and return false.
  3. Take the storages you need through the constructor; AvailableMigrations obtains them from SpResourceManager (see its constructor for the available I*Storage fields).
  4. Register it by appending it to the end of the list in AvailableMigrations.getAvailableMigrations(). Never insert between existing entries: migrations run in list order and installations may already be past earlier ones.
  5. Treat partial failure explicitly — log and rethrow rather than leaving a half-migrated state silently.

Rules

  • Preserve startup behaviour for both OAuth and non-OAuth deployments.
  • Do not put long-running or blocking work on startup thread paths.

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.