← all publishers

iyoda

@iyoda source repo

Report this profile Claim this profile

• 4 skills
• 0 followers
• 10 hours ago last updated

1. ▌
   Optimize Test Suite · iyoda bundle

   Diagnose and improve redundant, slow, flaky, or poorly partitioned automated test suites while preserving failure-detection strength and behavior coverage. Use when Codex needs to profile test duration, identify duplicated assertions or scenarios, consolidate tests and fixtures, reduce unnecessary setup, I/O, subprocess, database, network, or framework overhead, improve fast-versus-integration suite boundaries, or demonstrate measurable test-runtime improvement without weakening regression protection.
   0 installs
2. ▌
   Developer Experience · iyoda bundle

   Audit and improve developer-facing documentation, language tooling, editor support, formatting, linting, test granularity, test doubles, and contributor commands while preserving runtime behavior. Use when a repository needs clearer onboarding, reliable language-server or type-checker feedback, less noisy or faster lint checks, a balanced unit-to-external test strategy, consistent local and CI workflows, or a measured developer-experience cleanup.
   0 installs
3. ▌
   Prune Stale Guidance · iyoda bundle

   Remove obsolete, superseded, duplicated, misleading, archive-only, or contextless identifier-based rules and prose from the working tree while preserving current behavior and authoritative constraints, using Git history as the historical record. Use for cleanup requests involving AGENTS.md, README files, runbooks, policies, architecture notes, plans, archive documents, configuration comments, code comments, or other maintained text where stale instructions must be safely deleted, consolidated, minimally repaired, or rewritten from opaque labels such as G007, US-001, AC-6b, phase codes, gate IDs, or retired ticket names into self-explanatory language.
   0 installs
4. ▌
   Map Orphaned Identifiers · iyoda bundle

   Inventory opaque temporary identifiers such as G007, US-001, AC-6b, gate and phase codes, or short labels such as A1b; recover their present-day meanings from the working tree and Git history; classify orphaned, explained, machine-consumed, ambiguous, and historical-only occurrences; and save or update a repository-local meaning map. Use when identifiers need evidence-backed clarification before documentation cleanup or migration. Do not use for the cleanup itself when the requested outcome is to delete or rewrite stale guidance.
   0 installs