Skip to content

Releases: Talibabtou/website-shower

v1.1.0 - Clawpatch methodology inspirations

Choose a tag to compare

@Talibabtou Talibabtou released this 24 Jun 18:11

v1.1.0 Release Notes

Website Shower v1.1.0 sharpens the audit workflow without changing the read-only default.

Added

  • Website map-first audit step.
  • scripts/scan-website-map.sh for app roots, routes, feature roots, API/data boundaries, tests, generated output, packages, and checker signals.
  • Required inspected-scope section in reports.
  • Optional website-shower-report.json shape for host tools and later reruns.
  • Lightweight lifecycle guidance for open, accepted, fixed, ignored, and false-positive tasks.
  • Boundary markers such as client-server, external-api, package-boundary, state-store, generated-code, env-config, auth-session, database, framework-entrypoint, and design-system.

Kept

  • Markdown checklist remains the default report.
  • Source/config files remain read-only unless the user explicitly asks for fixes.
  • Scanner output remains candidate evidence, not automatic findings.

v1.0.0 - Wesbite Shower Initial Release

Choose a tag to compare

@Talibabtou Talibabtou released this 24 Jun 14:21

v1.0.0 Release Notes

First full Website Shower release.

Included

  • Read-only website maintenance skill for agents.
  • Multi-module scanner that gathers candidate evidence before judgment.
  • Modules for file tree hygiene, monorepo ownership, TypeScript hygiene, React/Next habits, Tailwind/CSS cleanup, component hygiene, API contracts, data fetching, state/domain contracts, naming drift, dependency hygiene, performance, types/constants, and unused-code leads.
  • Checklist report format for human or agent follow-up.
  • Anonymous fixture and smoke test.
  • Canonical compact adapter rule with generated agent adapters.
  • Agent support for Codex, OpenCode, OpenClaw, Copilot, Cursor, Windsurf, Cline, Kiro, .agents, and AGENTS.md consumers.

Validation

  • Fixture scan produces a full Website Shower checklist report without editing files.
  • npm test checks scanner syntax, adapter sync, and fixture smoke output.
  • Real-repo validation has been tested during development on clean, complex, and monorepo website repos.

Boundaries

  • Scanner output is candidate evidence only.
  • The default workflow is read-only.
  • Reports must include file evidence, change risk, and validation steps before edits.
  • Same literal values can still need separate owner constants when database enums, tables, or lifecycle ownership differs.

Install

git clone https://github.com/Talibabtou/website-shower.git ~/.codex/skills/website-shower

From a checkout:

scripts/install-agent.sh codex
scripts/install-agent.sh all-local /path/to/project

v0.1.0 - Concept Initial release

Choose a tag to compare

@Talibabtou Talibabtou released this 23 Jun 13:19

v0.1.0 Release Notes

Initial release of types-constants-audit.

Included

  • Codex skill for read-only TypeScript type and constant audits.
  • Bash scanner for candidate type/constant files, repeated literals, literal unions, repeated type/interface names, large files, and exported constants to usage-check.
  • Placement rules for inline, feature-local, app-global, and shared contracts.
  • Signal/noise heuristics for monorepos, generated files, repeated primitives, and local prop/state names.
  • Report format guidance.
  • Anonymous fixture and smoke test.
  • Example before/after audit report and reusable report template.
  • Agent compatibility files for Codex, OpenCode, OpenClaw, Copilot, Cursor, Windsurf, Cline, Kiro, .agents, and AGENTS.md consumers.

Validation

  • Fixture validation produced 5 findings/leads without editing files.
  • Installed Codex skill validation on a feature-oriented TypeScript website produced 4 useful read-only findings.
  • Tested previously on a clean Next.js app, a feature-heavy React app, and a large monorepo during development.
  • npm test passes.

Boundaries

  • The scanner prints candidates only; agents must inspect usage before reporting findings.
  • The default workflow is read-only.
  • Same literal values can still need separate owner constants when database enums, tables, or lifecycle ownership differ.
  • Phase-two website maintenance audits are intentionally out of scope for this release.

Install

git clone https://github.com/Talibabtou/types-constants-audit.git ~/.codex/skills/types-constants-audit