Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By skishore23
Enforces verification gates in Claude Code sessions — detects loops, requires proof of work, and blocks tool calls until evidence is collected and verified, supporting configurable off/warn/block modes.
npx claudepluginhub joshuarweaver/cascade-code-testing-misc --plugin skishore23-winkExecutes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Analyze Claude Code agent session transcripts to identify inefficiencies, anti-patterns, repeated mistakes, missing tooling opportunities, and user frustration signals for continuous improvement
Automatic context engineering — observes your coding sessions and generates rules, suggestions, skills, and hooks so Claude gets smarter on your codebase over time
Self-evolving Claude Code system that learns from corrections, manages context, and improves every session
Verification-first engineering toolkit for Claude Code. 15 skills across a 5-phase spine (Investigate → Design → Implement → Verify → Ship), 8 specialist agents, an interactive setup wizard. Every skill has rationalizations + evidence requirements. Built for senior ICs and tech leads.
Harness for Claude Code — skills, /harness:* slash commands, persona subagents, lifecycle hooks, and MCP tools without per-repo `harness setup`. Sibling plugins exist for Cursor, Gemini CLI, and Codex.
Personal Claude Code + Codex dev stack: security hooks, AI-first code conventions, /security-review, /repo-map, /stack-check, portable statusline. Designed to complement other skills-based plugins, not replace them.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Discipline & Insights for Claude Code
Enforces quality • Tracks context • Suggests improvements
Wink is a discipline plugin for Claude Code that:
Wink collects data and Claude reasons about it. You approve changes.
| Feature | What It Does |
|---|---|
| Intent Guardian | Silently captures task intent, verifies completion before stopping |
| Smart Verification | Skips irrelevant checks (e.g., no tests for docs-only changes) |
| Stop Discipline | Blocks stopping until verification passes |
| Baseline Awareness | Distinguishes pre-existing failures from regressions |
| Context Hygiene | Monitors wasted reads, loops, and session efficiency |
| Agent Suggestions | Suggests specialized agents based on metrics |
Option A: Claude Code Plugin (Recommended)
/plugin marketplace add skishore23/wink
/plugin install wink@wink
Option B: Manual
git clone https://github.com/skishore23/wink.git
cd wink && bun install && bun run build
Add to ~/.claude/settings.local.json:
{
"hooks": "/path/to/wink/hooks/hooks.json"
}
/setup
This will:
.wink/ directory and databasepackage.json scripts/verify
This runs your configured checks. If verifiers weren't auto-detected, edit .wink/config.json:
{
"verifiers": {
"typecheck": "npm run typecheck",
"lint": "npm run lint",
"test": "npm test"
}
}
.wink/
Look for this in your prompt responses:
○ wink · ✓ verified
Run /wink to see session analysis:
✦ wink · session analysis
node · 45 edits · 120 reads · 32min
hot folders
████████████ core (28)
████████ hooks (18)
context loss (files read 5+ times)
12x storage.ts
8x config.ts
context hygiene
███████████████ efficiency: 73/100
focus: 0.38 (120 read → 45 edited)
• 3 files read 3+ times
• 8 files read but never edited
agents
suggested
+ core-expert
28 edits in core/, 15 re-reads
current thresholds
folder-expert: 20
error-fixer: 3
context-keeper: 5
Based on this data, what improvements would you suggest?
Run /wink --apply to have Claude generate the suggested agents.
┌─────────────────────────────────────────────────────────────┐
│ │
│ Hooks collect data (reads, edits, errors) │
│ ↓ │
│ /wink shows raw metrics │
│ ↓ │
│ Claude analyzes and suggests improvements │
│ ↓ │
│ User approves, Claude applies │
│ │
└─────────────────────────────────────────────────────────────┘
| Metric | Purpose |
|---|---|
| Hot Folders | Directories with 20+ edits → agent candidates |
| Read Loops | Files read 3+ times → context-keeper suggestions |
| Error Patterns | Logged by category for analysis |
| Context Hygiene | Wasted reads, dead files, search efficiency |
| Verification | Pass/fail history |
Wink suggests six types of specialized agents:
| Agent | Trigger | Purpose |
|---|---|---|
| folder-expert | 20+ edits | Expert on specific folder patterns |
| context-keeper | 5+ reads | Cache file summaries to prevent re-reads |
| error-fixer | 3+ errors | Focus on recurring error patterns |
| lang-specialist | Project detected | Language expert (commands from config) |
| quality-guard | Failing checks | Fix quality hotspots |
| regression-fixer | Regressions | Restore checks that used to pass |
When you run /wink --apply, Claude automatically generates agents: