Jinsi gani wakala wa msimbo unaweza kurekebisha hitilafu, kuendesha mtihani, na kuwa na commit wakati wewe unabaki katika udhibiti?

Question

Accepted Answer

**Wakala** wa msimbo inaweza kuendesha marekebisho ya hitilafu kutoka mwanzo hadi mwisho — kurudia, kulokaliza, kurekebisha, kuthibitisha, commit — lakini unabaki katika udhibiti kwa njia ya **ruhusa ndogo, idhini ya mtu, na hatua ndogo zinazoweza kurudi nyuma**. Wakala hufanya kuandika; wewe unaamua nini halisi inayolanisha.

## Kitanzi

```text
1. REPRODUCE  → write/run a failing test that demonstrates the bug (red)
2. LOCATE     → search the codebase, read the relevant files, form a hypothesis
3. PROPOSE    → draft a minimal fix (you can review the plan before any edit)
4. VERIFY     → run tests + lint/typecheck → fix is proven by the test going green
5. REVIEW     → show the DIFF for your approval (nothing committed yet)
6. COMMIT     → only after approval, on a branch, with a clear message
```

Wazo kuu ni **uthibitisho unaoendeshwa na mtihani**: wakala hauamsemi "kurekebishwa" — huionyesha kwa kuufanya mtihani usiofaulu upite. Mtihani usiofaulu kutoka hatua 1 ni ishara ya lengo halisi kwamba mabadiliko yalifanya kazi.

## Mekanizmu za Udhibiti

```text
- SCOPED PERMISSIONS → allowlist safe commands (test, lint); prompt for the rest
- APPROVAL GATES     → human confirms destructive/irreversible actions + the final commit
- SMALL STEPS        → one focused change at a time → easy to review and revert
- BRANCH / WORKTREE   → work isolated from main; throw it away if it goes wrong
- DIFF REVIEW        → read the actual diff before commit, not just the agent's summary
```

```bash
# The agent runs the suite itself and reports the result before proposing a commit
npm test -- --runInBand   # red before the fix, green after → objective verification
git diff                  # you review every line that will be committed
```

Kuendesha katika **tawi au git worktree** inakumaanisha kesi mbaya zaidi ni `git checkout main` — jaribio haijawahi kugusa hali yako ya kufanya kazi. Commits ndogo zinazoweza kurudi nyuma zinafanya hatua yoyote rahisi kuchambua na kurudi nyuma.

## Kwa nini kina umuhimu

Msimbo wa wakala unabadilisha kutoka kuandika kila mstari hadi **kutathmini na kuelezesha**. Nguvu ni halisi, lakini vivyo hivyo ni hatari ya wakala kuzaa kwa ujinga mabadiliko yasioyofaa au yanayoharibu. Kuendelea na mlangoni wa idhini wa mtu kabla ya commits, kuthibitisha kwa mitihani badala ya kuamini mtanzu, na kutenganisha kazi katika tawi hukuruhusu kuchukua kasi ya automatisering wakati ukibaki yule anayeamua nini kinachofika `main`.