---
title: "Discussion on \"I Built a Tool That Refuses Commits. It Never Refused Itself.\" | Hashnode"
description: "Discussion on \"I Built a Tool That Refuses Commits. It Never Refused Itself.\". AI writes most of my code now. The parts I used to skip became the job, so I built the harness that keeps them."
url: "https://hashnode.com/posts/i-built-a-tool-that-refuses-commits-it-never-refused-itself/6afb5243dc17db4af258dda7"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [I Built a Tool That Refuses Commits. It Never Refused Itself.](https://jeelvankhede.hashnode.dev/i-built-a-tool-that-refuses-commits-it-never-refused-itself?utm_source=hashnode&utm_medium=feed)

AI writes most of my code now. The parts I used to skip became the job, so I built the harness that keeps them.

3d ago · 6 min read · jeelvankhede.hashnode.dev  
Read the article

-   [#ai-agents](https://hashnode.com/tag/ai-agents)
-   [#developer-tools](https://hashnode.com/tag/developer-tools)
-   [#software-development](https://hashnode.com/tag/software-development)
-   [#ai-workflow](https://hashnode.com/tag/ai-workflow)

## Written by

[Jeel Vankhede](https://hashnode.com/@jeelvankhede)

@jeelvankhede · Ahmedabad, India

  
[View profile](https://hashnode.com/@jeelvankhede)

Lead Full Stack Engineer, 10+ years. Building AI engineering-lifecycle tooling.

Lead Full Stack Engineer with 10+ years across frontend, backend, mobile, and architecture. I write about AI-assisted development, engineering workflows, and the tools I build to make agent-driven engineering more reliable, including agentsmyth, fare, and bare. 12k+ Stack Overflow reputation, 1.1M+ developers reached.

## Responses 3

Markdown supported · ⌘↵ to post

[Paul Pham](https://hashnode.com/@paulpham157)

[3d ago](https://hashnode.com/posts/i-built-a-tool-that-refuses-commits-it-never-refused-itself/6afb5243dc17db4af258dda7/comment/6afbcd9ef957962b46d6588a)

What stops the agent from writing the plan artifact itself and then passing check-lifecycle? Claude Code will happily edit files in that slug folder unless something blocks the path.

[Jeel Vankhede](https://hashnode.com/@jeelvankhede)

[2d ago](https://hashnode.com/posts/i-built-a-tool-that-refuses-commits-it-never-refused-itself/6afb5243dc17db4af258dda7/comment/6afbcd9ef957962b46d6588a#reply-6afc6f3221e4858ba7877109)

Noted! You are right. Nothing blocks it today. The gate checks that the plan has an approval section marked approved, with my words quoted. The agent writes that file, so it can write the approval too. I reproduced it: change two lines in the plan and the commit that was refused goes through with exit 0.

What the gate stops is an agent skipping or forgetting the checkpoint. It does not stop an agent that forges it. Closing that needs the approval to live somewhere the agent cannot write. That is not in the tool yet. I'll be releasing this in upcoming version.

[Paul Pham](https://hashnode.com/@paulpham157)

[2d ago](https://hashnode.com/posts/i-built-a-tool-that-refuses-commits-it-never-refused-itself/6afb5243dc17db4af258dda7/comment/6afbcd9ef957962b46d6588a#reply-6afc80493c1d18661f3f459b)

How exciting! Afterward, write a piece about the process.
