Skip to content
Skills Library
Programming · Review & audit

plugin-navigator

/plugin-navigator

Navigates between Jekyll plugin source files and their tests, reports file-level test presence, and finds missing or orphaned files. Use when working on Jekyll plugins or tests under `_plugins/` or `_tests/`, locating a corresponding test or plugin, or reviewing test coverage.

Author
agude ↗
Licence
MIT
Last repository change
18.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/lib/common.sh

What it does and when to use it

Navigates between Jekyll plugin source files and their tests, reports file-level test presence, and finds missing or orphaned files. Use when working on Jekyll plugins or tests under `_plugins/` or `_tests/`, locating a corresponding test or plugin, or reviewing test coverage.

Original author description

Navigates between Jekyll plugin source files and their tests, reports file-level test presence, and finds missing or orphaned files. Use when working on Jekyll plugins or tests under `_plugins/` or `_tests/`, locating a corresponding test or plugin, or reviewing test coverage.

How it works

  1. Find the corresponding file
  2. Review coverage and inventory
  3. Plugin domains
  4. When changing a plugin
  5. Review test comprehensiveness
Original SKILL.md headings · 141 lines, 693 words
SKILL.md preview
---
name: plugin-navigator
description: Navigates between Jekyll plugin source files and their tests, reports file-level test presence, and finds missing or orphaned files. Use when working on Jekyll plugins or tests under `_plugins/` or `_tests/`, locating a corresponding test or plugin, or reviewing test coverage.
---

# Plugin Navigator

Use the scripts in this skill to map plugin source files to tests and to
review whether the two trees stay aligned. Run them from the project root. The
scripts use Git to locate the project root and expect these paths:

- Plugin source: `_plugins/src/`
- Tests: `_tests/src/`

These checks measure the presence of matching test files. They do not run
tests or measure line, branch, or method coverage.

## Find the corresponding file

Use the script that matches the file you have:

```bash
# Find test file(s) for a plugin
.claude/skills/plugin-navigator/scripts/test-for-plugin \
  _plugins/src/infrastructure/url_utils.rb

# Find the plugin file for a test
.claude/skills/plugin-navigator/scripts/plugin-for-test \
  _tests/src/infrastructure/test_url_utils.rb
```

`test-for-plugin` accepts one plugin path under `_plugins/src/`. It prints
matching test paths. It checks both an exact test name and tests with a
suffix:

```text
_plugins/src/<path>/<name>.rb
_tests/src/<path>/test_<name>.rb
_tests/src/<path>/test_<name>_*.rb
```

If no test matches, it prints `MISSING` and exits with status 1.

`plugin-for-test` accepts one test path under `_tests/src/`. It prints the
matching plugin path. It first checks the full name after `test_`, then removes
underscore-separated suffixes from right to left until it finds a plugin. For
example, `test_link_cache_generator_favorites.rb` first checks
`link_cache_generator_favorites.rb`, then can resolve to
`link_cache_generator.rb`. If no plugin matches, it prints `ORPHAN` and exits
with status 1.

Because matching uses the plugin name as a prefix, a suffixed test such as
`test_user_profile.rb` also matches `user.rb`. Keep plugin names and test names
unambiguous when adding files.

## Review coverage and inventory

Run these commands from the project root:

```bash
# Show tested-plugin counts by domain and for the whole repository
.claude/skills/plugin-navigator/scripts/coverage-stats

# List plugins without a matching test
.claude/skills/plugin-navigator/scripts/coverage-stats --list-missing

# Group missing plugins by domain
.claude/skills/plugin-navigator/scripts/coverage-stats \
  --list-missing --by-domain

# List tests that do not resolve to a plugin
.claude/skills/plugin-navigator/scripts/orphan-tests
```

`coverage-stats` scans every Ruby file below `_plugins/src/`. In its default
mode, each domain is reported as `tested/total`; a plugin counts as tested when
at least one matching test file exists. `--list-missing` changes the output to
the missing plugin paths and a total. Adding `--by-domain` groups those paths
under domain headings.

`orphan-tests` scans every Ruby file below `_tests/src/`. It excludes the
cross-cutting test filenames intentionally allowlisted by the script:

- `test_helper.rb`
- `test_render_mode_coverage.rb`
- `test_link_cache_structure.rb`
- `test_architecture.rb`
- `test_markdown_output_includes.rb` (shared `_includes/` rendered in Markdown
  mode)
- `test_json_ld_rendered_site.rb` (SEO output built with a fixture site)
- `test_dark_mode_contrast.rb` (color contrast defined in
  `_sass/_variables.scss`)
- `test_skill_docs_paths.rb` and `test_skill_docs_yard_objects.rb` (paths and
  YARD objects referenced by skill documentation)
- `test_warning_filter.rb` (warning filtering in `_tests/test_helper.rb`)

When adding a cross-cutting test, add its filename to `ALLOWED_ORPHANS` in
`orphan-tests` and to this list.

## Plugin domains

The top-level directories under `_plugins/src/` are:

| Domain | Purpose |
| --- | --- |
| `infrastructure/` | Low-level utilities such as logging, URL and text processing, and the link cache. |
| `content/` | Site-domain logic for books, posts, authors, series, short stories, and markdown output. |
| `seo/` | JSON-LD generators, SEO meta tags, front-matter validation, and standard.site output. |
| `ui/` | Reusable components such as cards, ratings, citations, quotes, and tags. |

The test tree generally mirrors the plugin tree. Root-level tests under
`_tests/src/` are cross-cutting exceptions and may not have a corresponding
plugin file.

## When changing a plugin

1. Run `test-for-plugin` before editing to locate every existing test, and
   `make doc-show OBJ=<Class>` to read the class's tagged docs (`@gotcha`,
   `@validator`, `@pattern`, `@pipeline`). `make doc-index` lists every tagged
   object.
2. Add or update a test in the same relative directory. Use
   `test_<name>.rb` for the primary test or `test_<name>_<purpose>.rb` for a
   focused integration or edge-case suite.
3. Run each affected test through the repository task runner:

   ```bash
   make test TEST=_tests/src/path/to/test_file.rb
   ```

4. Run `coverage-stats --list-missing` and `orphan-tests` when changing file
   layout or adding a new plugin/test pair.

Do not invoke `jekyll`, `bundle`, or Ruby test files directly. Use `make`
commands for repository operations.

## Review test comprehensiveness

For a plugin with matching tests, check:

1. All public methods and other supported entry points.
2. Nil, empty, missing-data, invalid-input, and malformed-input cases where applicable.
3. Error paths and missing dependencies.
4. Boundary cases such as first/last items and single-item versus multi-item collections.
5. Integration with real or representative Jekyll site data.
Files in this package (6)
  • SKILL.md 6 KB
  • scripts/coverage-stats 2 KB
  • scripts/orphan-tests 1 KB
  • scripts/plugin-for-test 1 KB
  • scripts/test-for-plugin 1 KB
  • scripts/lib/common.sh 3 KB

Versions

The database has no other skills named plugin-navigator.

Database snapshot: 13.11.2026 · package version 2b515672a543 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100post-dev-test
    Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
  • 100generate-tests
    Use when you want to generate reusable Playwright .spec.ts test files from the app-navigator's app map and playbooks
  • 100generate-tests
    Use when you want to generate reusable Playwright .spec.ts test files from the app-navigator's app map and playbooks
  • 90atn-manage
    Use when plugins, or the files, skills, agents, MCP servers or rules of the installed or another plugin, need to be listed, created, changed or deleted, when an external plugin is to be imported into a plugin or updated, or when a plugin is to be taken from, updated from or…
  • 100test-sync
    Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.
  • 100test-sync
    Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.