Item detail
github.com

xwk-911/rulehook

xwk-911/rulehook is a developer tool in RepoRadar's AI Coding Workflow section, holding Gold tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 9.8 out of 10.

Score8.3
Popularity6.6
Riskconditional
TierGold
Score breakdown
Usefulness8.0
Novelty8.0
Momentum7.0
Maturity6.6
Open-source/build8.4
Evidence7.2
Workflow potential9.8
Setup ease6.4

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for developers who want AI coding assistants to follow house rules consistently instead of relying on reminder prompts that get ignored the moment a session goes sideways.

Who should use it

teams sharing Claude Code, Codex, or Cursor workflows developers trying to stop test-gaming and sloppy handoff behavior engineering managers defining repeatable AI coding policies operators who want portable hook behavior across multiple agent clients

Who should skip it

Skip xwk-911/rulehook if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.

About this signal

xwk-911/rulehook is tracked by RepoRadar as a developer tool in the AI Coding Workflow section. First seen 2026-06-21; the source record was last checked on 2026-06-21. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for xwk-911/rulehook are workflow potential (9.8) and open-source/build quality (8.4), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The xwk-911/rulehook record combines a 8.3/10 composite score with separate popularity (6.6), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.

Risk explanation

It can block or redirect agent actions during active coding sessions, so teams should review the configured judge model, fail-open behavior, and hook scope before enabling it broadly.

Evidence links
Closest alternatives / related signals
agent-guardrails claude-code codex cursor policy-hooks
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

44 dated snapshots retained from 2026-06-21 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score8.3 current · +0.0 net
Repository momentum5.5 current · -1.5 net
GitHub stars (observed)22 current · +0 net
GitHub stars22 exact observation
VersionNot reported by source
Last releaseNot reported by source
Maintenancemaintained
Current riskconditional
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-138.35.522conditionaltry nowmaintained
2026-08-128.35.522conditionaltry nowmaintained
2026-08-118.35.522conditionaltry nowmaintained
2026-08-108.35.522conditionaltry nowmaintained
2026-08-098.35.522conditionaltry nowmaintained
2026-08-088.35.522conditionaltry nowmaintained
2026-08-078.35.522conditionaltry nowmaintained
2026-08-068.37.0Not recordedconditionaltry nownot recorded
2026-08-058.37.0Not recordedconditionaltry nownot recorded
2026-08-048.35.522conditionaltry nowmaintained
2026-08-038.35.522conditionaltry nowmaintained
2026-08-028.35.522conditionaltry nowmaintained

Why the record changed

maintenance changed

Maintenance changed: active → maintained.