gitwtfhub

wtf is surgical-dev-ops?

bonushora/surgical-dev-ops — explained in plain English

Analysis updated 2026-05-18

2Audience · developerSetup · easy

TL;DR

A set of protocol instructions you paste into an AI coding assistant to make it inspect code carefully, avoid big rewrites, and track context across sessions.

Mindmap

mindmap
  root((surgical-dev-ops))
    What it does
      AI behavior protocols
      Safe code evolution
      Session continuity
    Tech stack
      Markdown docs
      Protocol files
    Use cases
      Inspect before edit
      Minimal diffs
      Session snapshots
    Audience
      Developers using AI
      AI assisted teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Give an AI assistant a strict protocol to inspect existing code before changing it.

REASON 2

Keep an AI assistant from rewriting working code it was not asked to touch.

REASON 3

Carry decisions and context forward across multiple AI coding sessions using a snapshot summary.

REASON 4

Apply a consistent safe-editing discipline to an AI assistant across mobile, web, or backend projects.

What's in the stack?

MarkdownAI protocols

How it stacks up

bonushora/surgical-dev-ops0-bingwu-0/live-interpreter010zx00x1/faresnipe
Stars222
LanguagePythonPython
Setup difficultyeasymoderateeasy
Complexity2/52/5
Audiencedevelopergeneralgeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

README is in Portuguese by default, with an English version linked in the repo.

Wtf does this do

Surgical DevOps is not a piece of software you install and run. It is a set of written rules, called protocols, meant to be given to an AI coding assistant so it behaves more carefully when it changes existing code. The README is written in Portuguese, with an English translation also included in the repository. The project defines two protocols. The first, called BH-SEP, tells an AI to inspect existing code before changing anything, to preserve working code instead of rewriting it, to make the smallest possible changes, and to check its work after each step rather than making a pile of edits at once. The second, called BH-SDP, deals with keeping track of decisions and context across separate coding sessions, by having the AI produce a structured summary, called a snapshot, of what was decided and what files were touched, so the next session can pick up where the last one left off. To use it, you copy a ready made block of instructions into your AI assistant that points it to the two protocol files hosted on GitHub and tells it to follow them strictly for the rest of the session. The assistant is expected to confirm it has understood the rules before continuing. The author describes this as language and framework independent, meant to apply to mobile apps, web apps, backend systems, and infrastructure code alike, wherever AI assistance is used to modify an existing codebase. The stated goal is to reduce bugs and regressions caused by an AI assuming things about a system it has not actually inspected, while keeping the human in charge of engineering decisions.

Yoink these prompts

Prompt 1
Adopt the BH-SEP and BH-SDP protocols from surgical-dev-ops for this session and confirm you understand them
Prompt 2
Explain the difference between the BH-SEP and BH-SDP protocols in this repo
Prompt 3
Before editing this file, inspect the existing code fully and propose only a minimal diff
Prompt 4
Generate a snapshot of our session's decisions and next steps using the BH-SDP format
Prompt 5
Translate the BH-SEP protocol principles into a short checklist I can reuse

Frequently asked questions

wtf is surgical-dev-ops?

A set of protocol instructions you paste into an AI coding assistant to make it inspect code carefully, avoid big rewrites, and track context across sessions.

How hard is surgical-dev-ops to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is surgical-dev-ops for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.