unix-goto-development_skill

Overview

This skill provides expert guidance for developing the unix-goto shell navigation tool. It covers architecture, the standard 9-step feature workflow, testing to 100% coverage, performance optimization for sub-100ms navigation, and Linear issue integration. Use it as a practical checklist and implementation reference when adding features or optimizing unix-goto.

How this skill works

The skill inspects and codifies the unix-goto architecture: loader order, core navigation, cache/index, bookmarks, and history modules. It prescribes a 9-step workflow from planning through performance validation and Linear issue updates, plus test templates, module patterns, and cache behavior to meet strict performance and coverage targets. It also defines return codes, environment variable patterns, and commit formats for consistent contributions.

When to use it

• Adding a new unix-goto feature or module
• Implementing or optimizing the cache-index for O(1) lookups
• Writing tests to reach 100% coverage (unit, integration, edge, perf)
• Validating navigation performance (<100ms cached targets)
• Integrating feature work with Linear issues and proper commit metadata
• Documenting APIs and updating user README sections

Best practices

• Follow the 9-step feature workflow exactly: plan, create module, load, integrate, test, document API, update README, validate perf, update Linear and commit
• Respect critical load order in goto.sh so dependencies load before dependents
• Use provided module and test templates to ensure consistent style, globals, and return codes
• Aim for O(1) cache lookups and TTL-based cache validation; add auto-refresh for stale caches
• Write performance tests with explicit timing assertions and add benchmarks for regressions

Example use cases

• Implement a recent directories command with history-tracking dependency and <10ms retrieval
• Add a bookmarking subcommand with list/add/remove and API docs in docs/API.md
• Optimize cache-index.sh to improve cache hit rate and keep cached navigation <100ms
• Create a benchmark suite to validate cache build and lookup times and store CSV results
• Ship a feature with full tests, performance metrics, and a Linear issue update linking the commit