source-command-track-mentions

Use this skill when the user asks to run the migrated source command track-mentions.

Command Template

Track Mentions Workflow

Find new online mentions of either the Claude Code Ultimate Guide or the wider public project portfolio. The guide catalog lives in docs/media-mentions/mentions.yaml. The cross-project catalog lives in ~/Sites/perso/florian-portfolio/src/data/mentions.json.

Usage

/track-mentions            # Search + report new mentions, confirm before adding
/track-mentions --dry-run  # Search + report only, no YAML changes
/track-mentions --scheduled # Unattended report-only run, equivalent to --dry-run
/track-mentions --add-all  # Add all confirmed results after explicit approval in this session
/track-mentions --all-projects # Search the active GitHub portfolio and update the portfolio catalog
/track-mentions --commit   # Commit only the validated tracker files after an approved update

--scheduled always wins over write flags. A scheduled run must not edit files, create a commit, push, open a pull request, or publish a tracker update.

Step 1: Load existing tracker

For the default guide mode, read docs/media-mentions/mentions.yaml to get:

• Current meta.total_mentions count
• All existing url fields → build a deduplication set
• docs/media-mentions/review-queue.yaml → keep inaccessible candidates pending and rejected URLs excluded

For --all-projects:

1. Read the public FlorianBruniaux GitHub profile and list active repositories owned by that account.
2. Exclude forks, landing-only repositories, support repositories such as homebrew-tap, and RTK.
3. Read ~/Sites/perso/florian-portfolio/src/data/mentions.json to get tracked projects, source URLs, and existing multi-project assignments.
4. Treat one canonical URL as one source even when it names several projects.

Step 2: Run Perplexity deep research