agentleFS
wachterjohanneswachterjohannes/symfony-skills/skills/make-reset-password/SKILL.md

make-reset-password

Skill4 starsChanged 2 months agoMITView on GitHub

Use when users need a forgot-password flow that emails a reset link.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the bundle's behaviour of answering the request page identically whether or not the email exists.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Password reset

symfony console make:reset-password \
    --from-email-address=noreply@example.com --from-email-name="Acme" \
    --success-redirect-route=app_login

The two email values are required in a script: they have nothing to be derived from. The rest is usually guessed silently from security.yaml and the user class; when a guess is ambiguous the maker aborts naming the option to pass (--user-class, --email-field, --email-getter, --password-setter). Pass --success-redirect-route deliberately: the default is app_home, which is a guess about your route names, not a fact.

A user class must exist first (make:user). Install the maker if it is missing: symfony composer require --dev symfony/maker-bundle.

What you get

The flow comes from symfonycasts/reset-password-bundle, which the maker installs: a controller with the request, check-email and reset actions, two form types, the Twig templates, the reset email, and a ResetPasswordRequest entity holding the hashed tokens. That entity changes the schema, so a migration follows (make:migration).

What to check

  • The emails only leave the application when a mailer transport is configured; without a real MAILER_DSN the flow dead-ends silently in dev.
  • Keep the bundle's behaviour of answering the request page identically whether or not the email exists. Making the response say "no such account" turns the form into an account-enumeration oracle.

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.