Have Devin add a third-party token endpoint in your repo

A developer had Devin build a backend token endpoint from docs, then cleaned up the pull request through a few review cycles.

Done with Devin· Intermediate

What they did
Using Devin through Slack, the developer asked it to create a token-generation endpoint for an outside service and plug it into an existing microservice. They pointed Devin to the service docs and asked it to reuse the current CDK secret setup for the API key. Devin shared a plan, then opened a GitHub pull request. The developer reviewed it, left comments, and Devin pushed revisions.
How it went
After 2-3 rounds of review, the code was ready to ship, tests passed, and the pull request was merged. The whole job took about an hour, while the manual version would have taken about 15 minutes. The developer spent roughly 5 minutes on review.
Tips
Treat the pull request like a junior developer’s work: check key handling, code style, and whether new logic belongs in a shared library. Make the agent stop after opening the PR and wait for approval before any merge or other irreversible step.

Try it yourself with Devin

In [repo], add a backend endpoint for [third-party service] using [docs link] as the source of truth. Wire it into the existing [microservice name], and use the current [CDK secrets/env setup] for the API key. Match the code style and abstractions used in [relevant folder/file], add tests, and open a pull request with a short summary of the changes and any assumptions. Do not merge. Before making any irreversible change such as deleting, submitting, sending, or merging, pause and ask me to approve it.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on dev.to ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.