intelligent-claude-code

Activate when starting new work to check for established patterns. Activate when ensuring consistency with team standards or when promoting successful memory patterns. Searches and applies best practices before implementation.

Activate when user wants to save knowledge, search past decisions, or manage persistent memories. Handles architecture patterns, implementation logic, issues/fixes, and past implementations. Uses local SQLite + FTS5 + vector embeddings for fast hybrid search. Supports write, search, update, archive, and list operations.

Activate when user explicitly requests the development workflow process, asks about workflow phases, or says "start work", "begin development", "follow the process". Activate when creating PRs or deploying to production. NOT for simple questions or minor fixes. Executes AUTONOMOUSLY - only pauses when human decision is genuinely required.

Activate when reviewing code, before committing, after committing, or before merging a PR. Activate when user asks to review, audit, check for security issues, or find regressions. Analyzes code for logic errors, regressions, edge cases, security issues, and test gaps. Fixes findings AUTOMATICALLY. Required at process skill quality gates.

Activate when user asks to commit, push changes, create a PR, open a pull request, or submit changes for review. Activate when process skill reaches commit or PR phase. Provides commit message formatting and PR structure. PRs default to dev branch, not main. Works with git-privacy skill.

Activate when asked to auto-review and merge a PR. Runs a closed-loop workflow: subagent Stage 3 review -> fix findings -> re-review -> post ICC-REVIEW receipt -> merge (optional via workflow.auto_merge).

Activate when user asks to release, bump version, cut a release, merge to main, or tag a version. Handles version bumping (semver), CHANGELOG updates, PR merging, git tagging, and GitHub release creation.

Activate when performing git operations. MANDATORY by default - prevents direct commits to main/master, blocks destructive operations (force push, reset --hard). Enforces dev-first workflow where all changes go to dev before main. Assumes branch protection enabled unless disabled in settings.

Development guide for contributing to the Intelligent Claude Code (ICC) framework. Use when working on ICC source code, creating skills, updating hooks, or modifying behaviors.

Activate when user needs AI/ML work - model integration, behavioral frameworks, intelligent automation. Activate when @AI-Engineer is mentioned or work involves machine learning, agentic systems, or AI-driven features.

Activate when user needs architectural decisions, system design, technology selection, or design reviews. Activate when @Architect is mentioned or work requires structural decisions. Provides design patterns and architectural guidance.

Activate when a subagent completes work and needs continuation check. Activate when a task finishes to determine next steps or when detecting work patterns in user messages. Governs automatic work continuation and queue management.

Activate when user needs API or backend testing - REST/GraphQL validation, integration tests, database verification. Activate when @Backend-Tester is mentioned or work requires backend quality assurance.

Activate when user needs database work - schema design, query optimization, migrations, data modeling. Activate when @Database-Engineer is mentioned or work involves database design or performance tuning.

Activate when user asks to code, build, implement, create, fix bugs, refactor, or write software. Activate when @Developer is mentioned. Provides implementation patterns and coding standards for hands-on development work.

Activate when user needs CI/CD or deployment work - pipeline design, deployment automation, release management. Activate when @DevOps-Engineer is mentioned or work involves build systems or infrastructure automation.

Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.

Activate when performing git commits, creating pull requests, or any git operation. MANDATORY by default - prevents AI attribution (Co-Authored-By, "Generated with" footers). Does NOT block legitimate AI feature descriptions.

Activate when needing configuration values like git.privacy, autonomy.level, paths.*, team.default_reviewer. Retrieves ICC settings using dot notation from config hierarchy.

Activate when user asks about version, system status, "what version", or wants to verify ICC installation. Displays version, component status, and installation info.

Activate when performing infrastructure, VM, container, or cloud operations. Ensures safety protocols are followed and blocks destructive operations by default. Mirrors agent-infrastructure-protection hook.

Activate when setting up MCP servers, resolving MCP tool availability, or configuring fallbacks for MCP-dependent features. Configures and troubleshoots MCP (Model Context Protocol) integrations.

Activate when multiple independent work items can execute concurrently. Activate when coordinating non-blocking task patterns in L3 autonomy mode. Manages parallel execution from .agent/queue/.

Activate when user needs coordination, story breakdown, task delegation, or progress tracking. Activate when @PM is mentioned or work requires planning before implementation. PM coordinates specialists but does not implement.

Activate when user needs test planning or QA strategy - test frameworks, quality metrics, test automation. Activate when @QA-Engineer is mentioned or work requires comprehensive quality assurance approach.

Activate when user needs requirements gathering - business analysis, specification development, user stories. Activate when @Requirements-Engineer is mentioned or work requires bridging business and technical understanding.

Activate when user needs security work - vulnerability assessment, security architecture, compliance audits, penetration testing. Activate when @Security-Engineer is mentioned or work requires security review.

Activate when user wants to create a new skill or update an existing skill. Activate when extending capabilities with specialized knowledge, workflows, or tool integrations. Provides guidance for effective skill design.

Activate when user presents a large story or epic that needs decomposition. Activate when a task spans multiple components or requires coordination across specialists. Creates work items in .agent/queue/ for execution.

Activate when user asks for improvement suggestions, refactoring ideas, or "what could be better". Analyzes code and provides realistic, context-aware proposals. Implements safe improvements AUTOMATICALLY. Separate from reviewer (which finds problems).

Activate when user needs infrastructure or system operations work - system reliability, monitoring, capacity planning. Activate when @System-Engineer is mentioned or work involves configuration management or operational excellence.

Activate when facing complex problems, multi-step decisions, high-risk changes, complex debugging, or architectural decisions. Activate when careful analysis is needed before taking action. Provides explicit step-by-step validation.

Activate when user needs E2E or user journey testing - browser automation, Puppeteer/Playwright, cross-browser testing. Activate when @User-Tester is mentioned or work requires user flow validation or experience verification.

Activate when checking if work meets requirements, verifying completion criteria, validating file placement, or ensuring quality standards. Use before marking work complete to verify success criteria are met.

Activate when user needs UI/UX design work - interface design, user research, design systems, accessibility. Activate when @Web-Designer is mentioned or work requires visual design or user experience expertise.

Activate when user has a large task to break into smaller work items. Activate when user asks about work queue status or what remains to do. Activate when managing sequential or parallel execution. Creates and manages .agent/queue/ for cross-platform work tracking.

Activate when checking workflow step requirements, resolving workflow conflicts, or ensuring proper execution sequence. Applies workflow enforcement patterns and validates compliance.