GitHub CLI 2.95.0

你正在終端機前趕報告，突然需要快速確認專案裡某個設定檔的幾行內容，或是想看一下特定資料夾底下有哪些檔案？以往你可能得先用瀏覽器打開 GitHub 網站慢慢點，或是把整個專案下載到本機才能查看。這次新增了 repo read-file 與 repo read-dir 兩個新功能，讓你直接在終端機裡就能讀取專案檔案與資料夾內容。這就像在圖書館，你現在可以直接站在目錄櫃前查閱書名與特定章節，不用把整本書借回家慢慢翻。當你只想確認一下別人專案裡的 README（專案說明檔）寫了什麼，這正是你打 gh repo read-file 的時刻，不用花時間複製整個專案，就能直接在畫面上讀取內容。

你正在為 AI 助手安裝或升級新功能，卻擔心安裝到一半出錯，會把原本正常運作的工具搞壞？這次升級改良了技能安裝機制，在更新時會先在一個 temp dir（臨時資料夾）把檔案準備好，確認沒問題才進行 swap in-place（原地替換），避免升級中斷留下半殘的檔案。此外，如果你用 non-interactively（非互動模式，指程式自動執行不跳出確認提示的運行方式）進行安裝，系統也會自動列出所有可用技能，並支援自訂 CLAUDE_CONFIG_DIR 指向特定的設定檔存放目錄。這就像裝修店面，以前工人在營業走道上敲打，停電就留下一地爛攤子；現在他們在後台工坊組裝好新櫃子，半夜一次完美換上。當你想把 AI 設定檔改存到自訂路徑，這正是你設定 CLAUDE_CONFIG_DIR 的時刻。

當你打開專案的待辦清單，卻發現裡面塞滿了各種自動化工具產生的訊息，想把機器人發的項目快速挑出來看？以往在篩選由 bot（機器人，指自動化執行的程式帳號）所發送的 PR（拉取請求，要求合併程式碼變更的申請）或 Issue（問題回報，用來記錄臭蟲的項目）時，過濾選項藏得非常深。這次特別優化了這個功能在介面上的 discoverable（易於發現的特質），讓你一眼就能找到按鈕。這就像在凌亂的電子信箱裡，以前很難找到在哪裡篩選系統通知，現在介面上多了一個醒目的「依機器信件篩選」選項。這項優化讓你在尋找特定的機器人提報時，不再需要在一堆進階語法中瞎找過濾開關在哪裡。

當你遇到使用問題想查閱說明書，或是開發專案時需要最新、最穩定的底層套件支援？為了讓開發者有更好的體驗，這次調整對 discussion（討論區）的說明文件進行了細部修飾，讓新手更容易看懂如何使用。同時，專案也升級了 devcontainer（開發容器，提供統一開發環境的虛擬容器）底層的 Go 語言版本，並更新了多個安全與文字處理相關的 deps（相依套件，專案運作時需要引入的外部程式碼庫）版本。這就像定期為工廠的說明手冊更換破損書皮，並幫機器零件塗上防鏽油。雖然外表看不出劇烈變化，但整條生產線運轉起來卻更加流暢與安全。

Are you working in your terminal and need to quickly check the content of a configuration file in a repository, or see what files are in a directory? Previously, you had to open GitHub in a browser or clone the whole project locally. We've added two new features, repo read-file and repo read-dir, so you can inspect files and folders right from the command line. It's like standing at a library catalog card cabinet to check book titles or read specific chapters, without checking out the whole book. When you just want to check a remote project's instructions, that is when to run gh repo read-file, showing you the text instantly without cloning the project.

Are you installing or upgrading new functions for your AI helper, but worried that a failure midway might break your working tools? The installation process is now much safer by staging updates in a temp dir (temporary directory) and executing a swap in-place (atomic replacement) only when ready, preventing broken files from failed upgrades. During automated non-interactively (non-interactive, running without user prompts) setups, the system now lists all available skills and lets you customize the directory. It is like renovating a shop: workers used to hammer in open aisles and leave a mess if the power failed; now they assemble cabinets in a back workshop and swap them overnight. When you want to store configs in a custom path, that is when to set CLAUDE_CONFIG_DIR.

Are you searching through repository lists and wanting to quickly pull up everything submitted by bots? Previously, filtering PRs (pull requests, proposals to merge changes) or Issues (bug tracking items) by bot authors (automated accounts) was hard to find in the interface. We have made filtering by bot authors much more discoverable, bringing the filter option forward. It is like looking at a cluttered email inbox where you had to write search queries to single out machine mail; now, an obvious option to filter by machine senders is placed right in view, saving you the hassle of hunting for the toggle.

Are you looking up help files to solve a user problem, or needing the most stable background tools for your environment? To improve the developer experience, this update polishes the discussion help documentation for better clarity. We have bumped the Go language version in the devcontainer (development container providing unified environment) and upgraded various deps (dependencies, external libraries imported to run the app) to their latest versions. It is like replacing worn covers on instruction manuals and oiling machine parts. While these daily tasks bring no dramatic visual overhaul, they ensure the factory line runs smoothly and safely.