SETU · DEVELOPER EXPERIENCE · AWS + GITLAB
From merged code to reviewable documentation.
I designed and implemented Docs Agent to connect merged code changes with the documentation they affect. The AWS-hosted workflow proposes updates through GitLab merge requests, leaving the final decision with a reviewer.
The workflow gap
A code change can ship while its documentation waits for someone to notice the gap and prepare an update. Docs Agent starts from the merge event and produces a proposed documentation change for review.
A reviewable path
A GitLab webhook starts the workflow after a merge. Filter, validator, and verifier stages assess the change before the service generates a documentation update and opens a merge request for a person to review.
- 01 · START
GitLab merge
A webhook starts the workflow.
- 02 · ASSESS
Filter · validator · verifier
Named review stages assess the change.
- 03 · PROPOSE
Documentation update
The service prepares a proposed change.
- 04 · REVIEW
GitLab merge request
A person makes the final decision.
My contribution
I designed and implemented the stages that filter and evaluate changes, generate an update, and hand it back through GitLab for review.
What the result means
My résumé reports typical documentation turnaround falling from roughly two to four weeks to about one week.