Code Quality in Delivery: Review, CI, a Repo You Keep

Code quality on client work is a review, a pipeline, and a repository you keep. It is not a linter brand from a conference talk, and it is not a score we invent for a slide. If the only person who can merge is away, the process failed.

CodeLoop Studio in Sarajevo delivers that way on websites and products. A house versus a body shop is software house in Sarajevo. Taking over someone else’s repo is legacy takeover. WoodMeter is field software — quality is a build that runs on the device, not a Ruby style guide we do not use.

What we actually run

TypeScript on web. Kotlin and Swift on native. Tests on the paths that lose money or data. CI on the default branch. Pull requests with a second pair of eyes on auth, payments, and migrations. We will not pretend a formatter is a culture.

Next.js sites still need titles and speed — Next.js website build. Android UI we iterate in Compose — Android Compose UI.

What we freeze

• Your GitHub. You own the repo. Handover is not a subscription to our login.

• A green main. If CI is red for a week, we stopped. Status is written, not a vibe.

• Secrets stay out of git. Keys in the Console and the host you pay for. Not in a screenshot.

• No vanity “A+” reports. We will not sell a static analysis PDF as the product. The product is the next release you can ship.

AI in the editor is not a substitute

We use assistants to move faster. Review still happens. How we talk about that internally is vibe coding with AI. Product-facing AI is a different page — AI solutions.

Send the repo policy you already have

Who can merge, whether CI exists, and the next release that cannot slip. Reply in 24 hours — online estimate or contact.