<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Platform-Engineering on Onur Celep</title><link>https://onurcelep.github.io/tags/platform-engineering/</link><description>Recent content in Platform-Engineering on Onur Celep</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://onurcelep.github.io/tags/platform-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>The rule my agent broke while reading it: evals for AI skills</title><link>https://onurcelep.github.io/posts/ai-skill-evals/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>https://onurcelep.github.io/posts/ai-skill-evals/</guid><description>&lt;p&gt;My AI setup runs on rules. Release discipline, model routing, incident
playbooks — they ship to every agent session as &lt;em&gt;skills&lt;/em&gt;: markdown
instructions loaded into context, versioned in a
&lt;a href="https://github.com/onurcelep/ai-factory" class="external-link" target="_blank" rel="noopener"&gt;template repo&lt;/a&gt; and propagated
across my repositories. The &lt;a href="https://onurcelep.github.io/posts/how-i-work-with-ai-agents/" &gt;setup tour&lt;/a&gt; covers how that works; the
&lt;a href="https://onurcelep.github.io/posts/ai-agents-in-ci-silent-failures/" &gt;postmortem&lt;/a&gt; covers the
day the CI plumbing under it failed silently, and the guardrails that came
out of that.&lt;/p&gt;
&lt;p&gt;This post is about realizing the same failure class exists one layer up —
and what happened when I pointed tests at it.&lt;/p&gt;</description></item><item><title>The green check that did nothing: a postmortem of AI agents in CI</title><link>https://onurcelep.github.io/posts/ai-agents-in-ci-silent-failures/</link><pubDate>Sat, 11 Jul 2026 00:00:00 +0000</pubDate><guid>https://onurcelep.github.io/posts/ai-agents-in-ci-silent-failures/</guid><description>&lt;p&gt;I run AI coding agents in CI across my repositories. The loop looks like
this: I open a GitHub issue describing a change and tag the agent; it reads
the repo, makes the change on a branch, and hands me a pull request. A
second agent reviews every PR automatically before I look at it. A human
merges everything. The setup is stamped from a single template repo
(&lt;a href="https://github.com/onurcelep/ai-factory" class="external-link" target="_blank" rel="noopener"&gt;ai-factory&lt;/a&gt;) so all my projects
run the same configuration — the full tour of that setup and how it came
to be is &lt;a href="https://onurcelep.github.io/posts/how-i-work-with-ai-agents/" &gt;its own post&lt;/a&gt;; this
one is about the day it broke.&lt;/p&gt;</description></item><item><title>One AI setup for every repo: how I work with coding agents, and why it became a factory</title><link>https://onurcelep.github.io/posts/how-i-work-with-ai-agents/</link><pubDate>Wed, 08 Jul 2026 00:00:00 +0000</pubDate><guid>https://onurcelep.github.io/posts/how-i-work-with-ai-agents/</guid><description>&lt;p&gt;I write software with AI agents in three places: a terminal session while
I work, cloud sessions I fire off and forget, and agents that live in my
repos&amp;rsquo; CI. All three follow the same committed rules, read the same
committed memory, and hand everything to me as a pull request that I
merge. This post is a tour of that setup — what each piece is for, what
actually changed in how I work, and why keeping it consistent across
repositories eventually forced me to build a small platform for it
(&lt;a href="https://github.com/onurcelep/ai-factory" class="external-link" target="_blank" rel="noopener"&gt;ai-factory&lt;/a&gt;).&lt;/p&gt;</description></item><item><title>About</title><link>https://onurcelep.github.io/about/</link><pubDate>Fri, 09 Dec 2022 00:00:00 +0000</pubDate><guid>https://onurcelep.github.io/about/</guid><description>&lt;h2 id="who-i-am"&gt;
 Who I am?
 &lt;a class="heading-link" href="#who-i-am"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;A passionate software engineer with 10+ years of experience. A detail-oriented, communicative, adaptable engineer who specializes in analysis, design, and implementation of CI/CD and software test automation systems. Contributed development process of several high-volume and revenue software products. Interested in cloud systems, CI/CD, performance &amp;amp; automation test development areas.&lt;/p&gt;
&lt;h2 id="my-career"&gt;
 My Career
 &lt;a class="heading-link" href="#my-career"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;h3 id="software-consultancy"&gt;
 Software Consultancy
 &lt;a class="heading-link" href="#software-consultancy"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h3&gt;
&lt;p&gt;Providing technical consultancy and leadership services in CI/CD design and implementation, release management and
automation, data visualization, root cause analysis, technical way of working and KPI definition, team building areas.&lt;/p&gt;</description></item></channel></rss>