skills.rest
agude
agudeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plugin-navigator

Map Jekyll plugins to tests and report untested code and orphan tests.

7|8|Updated Feb 14, 2016
Search Tags:#codebase#bash#plugins#navigate#test-coverage#tests
One-click install
npx skills add https://github.com/agude/agude.github.io --skill plugin-navigator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-navigator
Source: https://github.com/agude/agude.github.io/tree/main/.claude/skills/plugin-navigator
Command: npx skills add https://github.com/agude/agude.github.io --skill plugin-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Navigate between Jekyll plugins and their tests to quickly identify untested code and review test coverage across the project.

Core Features & Use Cases

  • Navigate between plug-ins sources (_plugins/src/) and tests (_tests/src/).
  • Locate untested modules and assess test coverage using the built-in scripts.
  • Identify orphan tests (tests without a matching plugin) to keep the codebase clean.

Quick Start

From project root, run the following commands: .claude/skills/plugin-navigator/scripts/test-for-plugin _plugins/src/infrastructure/url_utils.rb .claude/skills/plugin-navigator/scripts/plugin-for-test _tests/src/infrastructure/test_url_utils.rb .claude/skills/plugin-navigator/scripts/coverage-stats .claude/skills/plugin-navigator/scripts/coverage-stats --list-missing .claude/skills/plugin-navigator/scripts/coverage-stats --list-missing --by-domain .claude/skills/plugin-navigator/scripts/orphan-tests

Frequently Asked Questions about plugin-navigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find untested plugins in a Jekyll codebase?▼

You can find untested plugins by running the coverage-stats script with the --list-missing flag to scan _plugins/src/ and report modules lacking corresponding tests in _tests/src/.

How do I check if a specific plugin has a corresponding test file?▼

Run the test-for-plugin script from your project root, passing the plugin path like _plugins/src/infrastructure/url_utils.rb, to discover its matching test file in the _tests/src/ directory.

What is the best way to identify orphan tests in my project?▼

The best way to identify orphan tests is to run the orphan-tests shell script, which scans _tests/src/ to flag any test files lacking a corresponding plugin source in _plugins/src/.

Can I group missing test coverage by domain instead of listing individual files?▼

Yes, you can group missing test coverage by domain by executing coverage-stats --list-missing --by-domain, which aggregates untested plugin reports across different infrastructure areas.

Does the plugin navigator work with codebases that lack a _plugins/src/ directory?▼

No, the navigator requires a standard Jekyll structure containing both _plugins/src/ and _tests/src/ folders to correctly map and verify plugin-test pairings using its shell scripts.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

update-codemap

Refresh CODEMAP documentation by scanning src/ and updating docs/technical/CODEMAP.md.

Community
Intermediate
sunholo-datasunholo-data
33

Test Coverage Guardian

Analyze test coverage to identify gaps, dead code, and brittleness.

Community
Intermediate
flutterflutter
2.8k

dart-skills-lint-setup

Configures dart_skills_lint for automated validation of AI agent skill directories.

Official
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic