chore(skills): Sharpen repomix-explorer description

[yamadashy]

Summary

Rewrites the repomix-explorer skill description so it activates more precisely, modeled on the description style in GoogleChrome/modern-web-guidance.

• Switch from a single-line string to a block scalar for readability.
• List Trigger for: cases by category (structure/overview, pattern discovery, metrics, remote repos) with concrete example phrasings.
• Add an explicit DO NOT trigger for: list (single-file edits, known-path greps, single-symbol lookups, git/test/build ops) to prevent over-triggering on targeted work.

Skill body is unchanged; this only refines the activation description.

Checklist

• Run `npm run test`
• Run `npm run lint`

🤖 Generated with Claude Code

[github-actions]

⚡ Performance Benchmark

Latest commit:	35c2e86 chore(skills): Address PR review feedback
Status:	✅ Benchmark complete!
Ubuntu:	0.67s (±0.03s) → 0.68s (±0.01s) · +0.00s (+0.3%)
macOS:	0.39s (±0.03s) → 0.40s (±0.04s) · +0.00s (+1.0%)
Windows:	0.87s (±0.01s) → 0.88s (±0.01s) · +0.00s (+0.5%)

Details

• Packing the repomix repository with node bin/repomix.cjs
• Warmup: 2 runs (discarded), interleaved execution
• Measurement: 20 runs / 30 on macOS (median ± IQR)
• Workflow run

History

3c84e75 chore(skills): Sharpen repomix-explorer description with trigger boundaries

Ubuntu:	0.52s (±0.01s) → 0.52s (±0.01s) · +0.00s (+0.0%)
macOS:	0.41s (±0.03s) → 0.40s (±0.02s) · -0.00s (-1.0%)
Windows:	0.92s (±0.01s) → 0.92s (±0.02s) · -0.00s (-0.2%)

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 66fa88d7-e560-47db-92d7-35e8fbbadf8b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Updated repomix-explorer skill documentation to clarify trigger criteria. The description changed from a single-line guidance to a detailed multi-line specification explicitly listing when the skill should trigger (repo structure queries, cross-repo patterns, metrics, remote URLs) and when it should not (code editing, known file lookups, grep-solvable searches, git/build operations).

Changes

Skill Trigger Guidance Documentation

Layer / File(s)	Summary
Skill trigger guidance update skills/repomix-explorer/SKILL.md	Skill description expanded to explicitly enumerate trigger phrases and non-trigger cases, providing clear boundaries for when repomix-explorer should activate.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• [-claude__skills__browser-extension-developer] Fix #1: Description needs trigger phrases #1038: Both changes modify SKILL.md frontmatter description to add trigger phrases, suggesting a pattern of refining skill trigger guidance across the repository.

Possibly related PRs

• yamadashy/repomix#1103: Both PRs update the skills/repomix-explorer skill documentation, with PR #1103 initially adding the repomix-explorer agent skill guide and this PR refining the skill description triggers.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(skills): Sharpen repomix-explorer description' directly and clearly summarizes the main change—refining the description of the repomix-explorer skill for better precision.
Description check	✅ Passed	The description covers the key changes (rewriting the skill description, adding trigger/do-not-trigger lists) and includes the required checklist, though items remain unchecked.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/explorer-description

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates the repomix-explorer skill definition to provide more detailed usage guidelines, including specific triggers and exclusion criteria. The feedback suggests clarifying that certain 'DO NOT trigger' rules apply only to the local project, as the skill remains necessary for accessing files or symbols in remote repositories where standard local tools like grep cannot be used.

[cloudflare-workers-and-pages]

Deploying repomix with    Cloudflare Pages

Latest commit:	35c2e86
Status:	✅  Deploy successful!
Preview URL:	https://21017809.repomix.pages.dev
Branch Preview URL:	https://chore-explorer-description.repomix.pages.dev

View logs

[claude]

Review Summary

Reviewed across code quality, security, performance, tests, conventions, and holistic angles. Description-only changes — no blocking issues. The | literal block scalar is the right choice (folding with >- would collapse the bullet lists). Title follows Conventional Commits. No tests reference skills/repomix-explorer/SKILL.md, so coverage is N/A. Token overhead is ~150 tokens per session, easily justified by avoiding spurious npx repomix@latest invocations on tasks better served by grep/Read.

One substantive ambiguity is worth addressing — and it's adjacent to what gemini-code-assist raised.

Details

Real ambiguity: the grep boundary in local repos

Trigger for line 8 includes "find all auth code", while DO NOT trigger for line 15 says "Single-symbol lookups in the local project answerable with one grep". In a local repo, find all auth code is also answerable with grep -iE "auth|login|password|token" — exactly the pattern this skill's own body recommends (line 170). So the same phrase appears on both sides depending on whether the repo is remote or local, and the rule isn't stated explicitly.

Concretely, the skill body already implies the rule (Step 1 distinguishes remote vs. local pack commands), but the activation description doesn't. Suggested clarification at the top of Trigger for:

- Remote repos: any github.com URL or "owner/repo" — always trigger
- Local repos: only when the question spans many files or needs aggregated metrics; otherwise prefer Read/grep

This collapses the apparent overlap and directly addresses the gemini-code-assist comment that "DO NOT trigger" rules should be local-scoped.

Minor wording inconsistency

Line 13 says "in the current project" while lines 14–15 say "in the local project". Same meaning — pick one for consistency. local project reads more clearly alongside Remote repos.

Out-of-scope (no action needed)

• Sibling SKILL.md files use three different description styles (|, >-, single-line, plain). This PR introduces the first | form, which is appropriate because it's the only one with structured bullet sub-sections. Not a problem.

Note: gh api .../comments was not accessible in this run, so I could not reply individually to the gemini-code-assist or coderabbitai inline threads. The gemini-code-assist suggestion is partially addressed already (2 of 4 "DO NOT" bullets carry the local qualifier) and the wording fix above closes the remaining gap.