Stats
Actions
Tags
From feature-flow
Enforces Kotlin/Android coding standards: auto-formats via ktlint/detekt on Stop, blocks edits to build/generated files, validates .kt files for forbidden patterns (!!, runBlocking, println, Log), and checks for Android CLI tools on session start.
4 events · 15 hooks
Safety signals detected in this hook configuration
Where this hook configuration is defined
Defined in hooks/hooks.json
Event handlers and matchers — expand Raw Configuration for the full JSON
node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/quality-gate.js180msWritenode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/context7-reminder.jsnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/antipattern-gate.jsEditnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/antipattern-gate.jsAgentnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/model-param-gate.jsTasknode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/model-param-gate.jsSkillnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/verdict-gate.jsWritenode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/plan-reminder.jsnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/console-warn.jsnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/lint-file.js30msEditnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/console-warn.jsnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/lint-file.js30msif [ -f .feature-flow.yml ]; then echo 'FEATURE-FLOW DEVELOPMENT ACTIVE: Use start: to begin any non-trivial work — it orchestrates the full lifecycle (design → verify → implement → ship). Rules: (1) Every task in an implementation plan MUST include **Acceptance Criteria:** with machine-verifiable - [ ] items. After writing a plan, run verify-plan-criteria. (2) Before claiming any task is complete, run verify-acceptance-criteria to mechanically check all criteria against the codebase. (3) Before writing new code, query Context7 docs for current patterns — library IDs are in .feature-flow.yml under context7. (4) PreToolUse hooks deny (block) Write/Edit calls containing any types, as any, or empty catch blocks — fix before writing; Task/Agent dispatches missing an explicit model parameter are denied the same way. console.log/debug is a PostToolUse advisory warning, not a block, and is allowed during TDD. (5) Stop hook runs tsc, lint, type-sync, and test checks and blocks session end on failures; per-file lint warnings from the PostToolUse hook remain advisory and do not block. (6) Tool API: Skill tool params are skill and args (NOT skill_name/arguments). Deferred tools (TaskCreate, TaskUpdate) must be loaded via ToolSearch before use. See references/tool-api.md for all tool syntax. Type "start: <description>" or "start: <description> --yolo" to begin.'; if ! grep -q 'context7:' .feature-flow.yml 2>/dev/null; then echo ''; echo 'UPGRADE NOTICE (v1.6.0): Your .feature-flow.yml is missing the context7 field. Run start: to auto-detect Context7 library IDs for your stack, or add them manually. New in v1.6.0: Context7 doc lookups, coding-standards.md, Study Existing Patterns step, Self-Review step, anti-pattern blocking hooks. See CHANGELOG.md for details.'; fi; else echo 'FEATURE-FLOW is installed. It helps you build features without mid-implementation surprises by adding a design and verification layer before you code. To start, just describe what you want to build: "start: add user notifications" -- feature-flow will auto-detect your tech stack, resolve Context7 documentation libraries, classify the scope, and walk you through the right steps. For a quick bug fix, just describe the problem — the lifecycle is lightweight: understand, fix, verify, commit. Type "start: <your idea, issue, or bug>" to get started. Add --yolo to auto-select defaults.'; finode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/version-check.jsnode ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/advisor-hint.jsnpx claudepluginhub uta2000/feature-flow --plugin feature-flow13plugins reuse this hooks config
First indexed Dec 29, 2025
Showing the 6 earliest of 13 plugins