marcusquinn/aidevops：README 來源編輯指南

marcusquinn/aidevops 的 README 將專案描述為「Vibe-Coding is easy. DevOps is hard. OpenCode & Git token-efficient AI agent automation for your app, business, and personal development. Opinionated tools, services, CLI & API stack for speed, security, and 24/7 results. Open-source first.」。本文只整理倉庫可直接核對的內容，不把 star、Fork 或宣傳語當成品質證明。README 在「AI DevOps Framework」下寫到：aidevops.sh plugin and AI DevOps framework for people who want AI to do useful work across code, infrastructure, business, marketing, content, and creative projects without turning every job into another long, fragile chat.。這說明的是專案邊界，不是已完成的生產驗證。

從 README 的「The Aim」與相關條目，可以先判斷它是否處理你的實際問題：Spend tokens and model budget deliberately. Cheap and fast models should handle routine work; stronger models should handle judgement, architecture, review, and risk.。若需求不同，不應只因專案熱度就採用。本文保留原始專案名、命令與元件名，方便回到一手來源核對。 README 另外列出一項可核對的資訊：Load the right context when it is needed, instead of stuffing every agent, skill, and tool into the prompt.。這類原文條目可用來設計試跑步驟，但不能取代實際環境測試。

README 將運作方式分散在「AI DevOps Framework」等段落。可確認的線索包括：> Recommended setup: OpenCode remain fully supported, and other model providers are evaluated from time to time as their quality, latency, and cost profiles change.。本文不把未寫出的架構、效能或安全邊界補成結論；真正的執行鏈仍要配合目錄、設定檔與版本標籤檢查。

第一次安裝應從 README 指出的入口開始。目前可核對的命令是： npm install -g aidevops && aidevops update 如果倉庫沒有命令，本文不會自行編造步驟，而是建議先閱讀「The Aim」，確認系統依賴、預設埠與首次初始化。

日常使用取決於專案文件。README 的「AI DevOps Framework」段落提到："Scope a mission to redesign the landing pages , break it into milestones, dispatch workers in parallel, validate each milestone, and track budget across the whole project."。設定檔、環境變數、權限與資料目錄只在來源明確時才會記錄；沒有寫出的預設值，應在測試環境驗證並保留回滾副本。 同一部分也提到：Keep secrets out of chat. Credentials, tenants, scans, confirmations, and audit logs are part of the workflow, not an afterthought.。