What is buggy buggy-git-diff-specs.md?

A set of instructions for checking code changes against the intent described by a Git commit. Git is the version-control system used to record code changes; the instructions infer expected behavior from the commit message and investigate changed functions.

Use it when checking a branch, commit, or recent diff, especially after requests such as verifying changes or looking for bugs.

It helps catch bugs introduced by a recent commit instead of reviewing the changed lines without knowing what they were meant to do.

How himanshusaini-afk/buggy configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to himanshusaini-afk/buggy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/himanshusaini-afk/buggy/main/.kiro/steering/buggy-git-diff-specs.md

Clone the repo

git clone --depth 1 https://github.com/himanshusaini-afk/buggy

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-git-diff-specs/github.svg)](https://agentmods.dev/instructions/himanshusaini-afk/buggy/buggy-git-diff-specs)

Your own site

<a href="https://agentmods.dev/instructions/himanshusaini-afk/buggy/buggy-git-diff-specs"><img src="https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-git-diff-specs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/himanshusaini-afk/buggy/buggy-git-diff-specs"><img src="https://agentmods.dev/badge/instructions/himanshusaini-afk/buggy/buggy-git-diff-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 437 This file is loaded in full into every session.

When invoked 437 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00437	$0.00437
Opus 5	$0.00218	$0.00218
Sonnet 5	$0.00087	$0.00087
Haiku 4.5	$0.00044	$0.00044

Measured 4d ago against content hash e7645955df3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

buggy buggy-git-diff-specs.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.kiro/steering/buggy-git-diff-specs.md · 57 lines

What it actually says

Buggy — Specification Inference from Git Diff

When the user mentions a commit, branch, or asks to verify recent changes, infer specifications from the git context and run Buggy investigations.

Triggering Phrases

"check my recent changes"
"verify this commit"
"any bugs in what I just pushed?"
"analyze the diff"

Workflow

Step 1: Get the diff context

Run git diff HEAD~1 --stat or git diff main...HEAD to see what changed. Read the commit message with git log -1 --format=%B.

Step 2: Infer intent from commit message

The commit message often reveals the specification:

Commit message	Inferred postcondition
"fix: handle empty array"	`items.length === 0 → result === defaultValue`
"feat: add discount capping"	`result >= 0, discount <= 100`
"refactor: extract helper"	Same behavior as before (no regression)
"perf: optimize calculation"	Same outputs for same inputs (behavioral equivalence)

Step 3: Investigate changed functions

For each function in the diff:

Infer specs from commit message + code context
Call buggy_investigate with those specs
Report any proven bugs in the new code

Step 4: Report findings

Commit: "feat: add bulk discount for large orders"
Changed: calculateSubtotal() in src/cart.ts

Inferred spec:
  Pre: items.length > 0, items.every(i => i.price >= 0)
  Post: result >= 0

Investigation result: ⚠️ Bug found
  Input: [{price: 0.5, quantity: 15}] → Output: -22.5
  The bulk discount (price - 2) goes negative for items under $2.

Fix available (8% overfitting): Add guard `item.price > 2`

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago First seen · 57 lines · 437 tokens per session scan A e7645955df3c

Subscribe to this mod's changes

buggy buggy-git-diff-specs.md is an instructions file published in the GitHub repository himanshusaini-afk/buggy (0 stars, last pushed 4d ago), licensed MIT. It adds 437 tokens to every session, about $0.0022 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.

Commits Debugging Git and workflow

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,126 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

buggy: Instructions file for Kiro