all publishers

clay-good

@clay-good source repo

37 published skills

  1. ▌
    Builder 2 · clay-good
    Code implementation specialist. Spawns to implement a specific feature, module, or function.
    359 repo stars
  2. ▌
    Verify All 2 · clay-good
    Run all quality checks — tests, lint, format, security scan.
    359 repo stars
  3. ▌
    Tester 2 · clay-good
    Test runner and fixer. Spawns to run the full test suite, diagnose failures, and fix them.
    359 repo stars
  4. ▌
    Explorer 2 · clay-good
    Codebase exploration and analysis specialist. Fast research before implementation.
    359 repo stars
  5. ▌
    Reviewer 2 · clay-good
    Security and code quality reviewer. Read-only deep review for vulnerabilities and quality issues.
    359 repo stars
  6. ▌
    Lint Fix 2 · clay-good
    Run the project linter and formatter, fix all violations.
    359 repo stars
  7. ▌
    Run Tests 2 · clay-good
    Run the full test suite, diagnose any failures, fix them, and re-run until green.
    359 repo stars
  8. ▌
    Update State 2 · clay-good
    Update .codelicious/STATE.md with accurate current status.
    359 repo stars
  9. ▌
    Openlore Debug 2 · clay-good
    Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
    359 repo stars
  10. ▌
    Openlore Generate 2 · clay-good
    Author a new OpenSpec domain specification from deterministic OpenLore MCP evidence. Use when asked to reverse-engineer, generate, or document a specification for existing code.
    359 repo stars
  11. ▌
    Openlore Brainstorm 2 · clay-good
    Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
    359 repo stars
  12. ▌
    Openlore Write Tests 2 · clay-good
    Write and run real tests for a function or spec scenario after reading implementation and contract evidence. Use when asked to add, improve, or repair tests without stubs or placeholders.
    359 repo stars
  13. ▌
    Openlore Plan Refactor 2 · clay-good
    Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
    359 repo stars
  14. ▌
    Openlore Review Changes 2 · clay-good
    Review code changes using OpenLore risk, call, coverage, and cluster evidence without editing code. Use when asked for a change review, pre-PR safety check, or merge recommendation.
    359 repo stars
  15. ▌
    Openlore Implement Story 2 · clay-good
    Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.
    359 repo stars
  16. ▌
    Openlore Analyze Codebase 2 · clay-good
    Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
    359 repo stars
  17. ▌
    Openlore Execute Refactor 2 · clay-good
    Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
    359 repo stars
  18. ▌
    Anvilate · clay-good
    Screen a mechanical or structural part against cited engineering checks with Anvilate, and report the result the way an engineer would. Use when asked to size, check, or validate a part, joint, member, or vessel, or to interpret an Anvilate scorecard.
    359 repo stars
  19. ▌
    Tester · clay-good
    Test runner and fixer. Spawns to run the full test suite, diagnose failures, and fix them.
    359 repo stars
  20. ▌
    Builder · clay-good
    Code implementation specialist. Spawns to implement a specific feature, module, or function.
    359 repo stars
  21. ▌
    Explorer · clay-good
    Codebase exploration and analysis specialist. Fast research before implementation.
    359 repo stars
  22. ▌
    Reviewer · clay-good
    Security and code quality reviewer. Read-only deep review for vulnerabilities and quality issues.
    359 repo stars
  23. ▌
    Lint Fix · clay-good
    Run the project linter and formatter, fix all violations.
    359 repo stars
  24. ▌
    Run Tests · clay-good
    Run the full test suite, diagnose any failures, fix them, and re-run until green.
    359 repo stars
  25. ▌
    Verify All · clay-good
    Run all quality checks — tests, lint, format, security scan.
    359 repo stars
  26. ▌
    Update State · clay-good
    Update .codelicious/STATE.md with accurate current status.
    359 repo stars
  27. ▌
    Openlore Debug · clay-good
    Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
    359 repo stars
  28. ▌
    Openlore Orient · clay-good bundle
    Retrieve relevant functions, callers, spec sections, and insertion points from OpenLore before reading source files. Use when starting work that needs structural orientation in an existing codebase.
    359 repo stars
  29. ▌
    Openlore Repair · clay-good
    Reconcile one existing OpenSpec specification from deterministic OpenLore MCP observations. Use when a spec may be incomplete, stale, partially covered, or orphaned from current code.
    359 repo stars
  30. ▌
    Openlore Generate · clay-good
    Author a new OpenSpec domain specification from deterministic OpenLore MCP evidence. Use when asked to reverse-engineer, generate, or document a specification for existing code.
    359 repo stars
  31. ▌
    Openlore Brainstorm · clay-good
    Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
    359 repo stars
  32. ▌
    Openlore Write Tests · clay-good
    Write and run real tests for a function or spec scenario after reading implementation and contract evidence. Use when asked to add, improve, or repair tests without stubs or placeholders.
    359 repo stars
  33. ▌
    Openlore Plan Refactor · clay-good
    Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
    359 repo stars
  34. ▌
    Openlore Review Changes · clay-good
    Review code changes using OpenLore risk, call, coverage, and cluster evidence without editing code. Use when asked for a change review, pre-PR safety check, or merge recommendation.
    359 repo stars
  35. ▌
    Openlore Implement Story · clay-good
    Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.
    359 repo stars
  36. ▌
    Openlore Analyze Codebase · clay-good
    Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
    359 repo stars
  37. ▌
    Openlore Execute Refactor · clay-good
    Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
    359 repo stars