Skip to main content
Discuss a project日本語

Original Bluesky post / the person's own explanation of the implementation path · Source language: English

The AI implements a request, and a person checks it in a preview

Andrew Lisowski automated the path from requests for his own app to a draft PR. He explains that he checks the implementation result and merges himself.

Who:
Andrew Lisowski, maker of Standard Reader
Scope:
A mechanism one person uses on their own app. The social post and the detailed article are treated as one observation
Source published:
2026-07-29
Period observed:
Start time not stated / social post July 29, 2026
Editorial check:
2026-10-23

Only the source ID is saved in this browser. Nothing syncs across devices.

What was confirmed

  • Publishes a path where marking a request "planned" runs through GitHub Actions and a Claude Routine to produce a draft PR.
  • The policy is to verify in code the assumptions written in the request, and to exclude question-only items from implementation.
  • He checks the diff and a PR-specific app and DB environment himself, directs necessary fixes, and then merges.

Who, and in what situation

Built a mechanism that, on receiving a user request, connects instructions to the AI with the start of implementation.

What they needed

Reducing the guidance of the AI by the developer that had been needed each time a request moved to implementation.

What they tried

Starting implementation and drafting are automated, while judging whether it is worth building, checking operation and merging remain human steps.

What this source lets you read

Recording together the steps handed to the AI and the places where judgment returns to a person makes practices easier to compare.

What to check next

From users' requests, how do you decide how far it may proceed automatically?

Limits of this source

  • A first-person report that also introduces a service they built.
  • The number of runs, success rate, effort reduction and failure rate are not stated.
  • The start date of the practice and the article's first publication date are unknown. The article shows an update date of July 29.

Read the primary source

Links use the original title or a HAKOMIRO source description. Japanese originals retain their published wording.

  1. First-person post about automating the implementation of Standard Reader feature requests (opens in new tab) ↗

    Andrew Lisowski/Bluesky /

    We checked the public HTML body and post time. It includes an introduction of a service they built.

  2. Atmospheric Automated Development (opens in new tab) ↗

    Andrew Lisowski / First publication date not stated / updated 2026-07-29

    The person's own operations report. There is no comparative measurement of effort or success rate.

← All sources