القائمة
Use when performing monthly tool audit of ubuntu-dev-ansible, checking for deprecated or redundant developer tools, or discovering new CLI tools that fit the dev profile
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | discover |
| description | Use when performing monthly tool audit of ubuntu-dev-ansible, checking for deprecated or redundant developer tools, or discovering new CLI tools that fit the dev profile |
Monthly audit and discovery sweep for the ubuntu-dev-ansible repo. Two phases: (1) audit installed tools for deprecation, redundancy, and suboptimal installs, (2) discover new tools matching the user's dev profile. Always complete audit before discovery — audit results inform what gaps exist.
Read these files to build a complete inventory of every tool currently installed:
roles/thibaut/vars/main.yml — tool lists: thibaut_apt_packages, thibaut_brew_packages, thibaut_uv_tools, thibaut_cargo_packages, thibaut_deb_packagesroles/thibaut/tasks/packages/*.yml — custom installer tasks (note: docker.yml and act.yml contain post-install side-effects only — the tools themselves are in the main vars)roles/thibaut/tasks/llm.yml — LLM-specific tools installed outside the main varsExtract every tool name and its install method. Present a brief summary:
Analyze the installed tools for issues. Use batched parallel WebSearch calls (issue multiple searches in one tool-call block).
Search categories (skip categories with no installed tools):
Budget: ~2 searches per relevant category (~12-16 total).
Example search queries:
Flag these issue types:
For each finding, record:
Calibration — the kind of findings you should catch:
These are real issues in the current config. Use them as a baseline for the level of analysis expected.
Complete the audit phase fully before starting discovery, since audit results inform what to suggest — no point recommending a tool if the audit already flagged a better alternative in that space.
First, read the discard log at discarded.md — tools the user rejected in previous runs. Everything on it is off the table for suggestions.
Search for new tools that fit the user profile but aren't installed. Use batched parallel WebSearch calls.
Budget: ~2 searches per category (~16 total). Prioritize categories where the current setup has fewer tools — that's where gaps are most likely.
Example search queries:
Filter criteria — only suggest tools that:
discarded.md) — the user already rejected theseFor each suggestion, record:
Target: 5-15 quality suggestions. Quality over quantity.
Calibration — the kind of tools you should find:
These are examples of real gaps in the current setup. Use them as a baseline for fit and quality.
Combine audit and discovery results into a single report:
## Tool Discovery Report — [today's date]
### Summary
- Audit: N findings (N deprecated, N superseded, N redundant, N suboptimal, N renamed)
- New tools: N suggestions across N categories
---
### Audit Findings
#### [Issue Type]
##### [Tool Name]
- **Status:** ...
- **Current:** ...
- **Recommendation:** ...
- **Source:** ...
(group by issue type, only show sections with findings)
---
### New Discoveries
#### [Category Name]
##### [Tool Name] — one-line description
- **Why it fits you:** ...
- **Install method:** ...
- **Popularity:** ...
- **Link:** ...
(group by category, only show categories with suggestions)
Handling sparse results: If web searches return nothing useful for a category, skip that category in the report. If an entire phase produces no results, still present the other phase. Never fail silently — always present whatever you found.
After presenting the report, ask:
"Which tools would you like me to add? Which should I discard (never suggest again)? Which audit recommendations should I act on? You can reference them by name or number."
For each tool the user selects:
Add to the appropriate list in roles/thibaut/vars/main.yml:
thibaut_apt_packages with a comment describing the toolthibaut_brew_packages with a comment describing the toolthibaut_uv_tools as - name: toolname # descriptionthibaut_cargo_packages with a commentMaintain alphabetical order within each section. Match the existing comment style.
Create a new file at roles/thibaut/tasks/packages/<tool-name>.yml. Two patterns exist — pick the simpler one that fits:
Pattern A — self-updating tools: Try upgrade first, install if not present. See packages/opencode.yml, packages/dprint.yml.
Pattern B — GitHub release tracking: Fetch latest version from GitHub API, compare with installed version, download if different, clean old versions. See packages/podman-desktop.yml, packages/awscli_v2.yml.
Always use changed_when to track actual changes.
Then add the include to roles/thibaut/tasks/installs.yml:
- name: Install <tool-name>
ansible.builtin.import_tasks: packages/<tool-name>.yml
tags:
- <tool-name>
If the tool needs configuration:
roles/thibaut/files/dotfiles/<config-path>roles/thibaut/tasks/system/dotfiles.yml (if needed)roles/thibaut/tasks/system/dotfiles.ymlRemove the tool from the appropriate list in roles/thibaut/vars/main.yml.
Append every tool the user chose to discard as a row in the discard log at discarded.md, sorted by tool name:
| Tool | Category | Reason | Date |
Use today's date. Record the user's reason if given, otherwise not selected. Step 3 reads this log, so a discarded tool never resurfaces.
Completion criterion: every tool the user discarded has a matching row in discarded.md.
If the tool needs PATH or env var additions, edit the block: content of the existing blockinfile task in roles/thibaut/tasks/system/dotfiles.yml (marker: # {mark} ANSIBLE MANAGED BLOCK: tools). Do not add a second blockinfile task.