faber-config
Load, validate, and resolve FABER configuration and workflows with inheritance support
Script and automate repetitive tasks and workflows.
Load, validate, and resolve FABER configuration and workflows with inheritance support
REQUIRED for all skill development. Automatically version control every skill file modification for rollback/comparison. Use after init_skill.sh, after every str_replace/create_file, and before packaging.
マーティン・ファウラーの『Refactoring』に基づくコード改善技術を提供するスキル。 外部動作を変えずに内部構造を改善する体系的手法を通じて、保守性・可読性を向上させる。 Anchors: • Refactoring (Martin Fowler) / 適用: 全般 / 目的: 体系的なリファクタリング手法 • Clean Code (Robert C. Martin) / 適用: 命名・構造 / 目的: 可読性向上 • Working Effectively with Legacy Code (Michael Feathers) / 適用: レガシー対応 / 目的: 安全なリファクタリング Trigger: Use when improving code structure, detecting code smells, reducing technical debt, or refactoring legacy code. refactoring, code smell, extract method, decompose conditional, technical debt, リファクタリング
Search GitHub code across millions of repositories using grep.app. Use when you need to find code patterns, implementations, examples, or understand how features are built in public codebases. (project)
Shared utilities for faber-cloud plugin - configuration loading, pattern resolution, auto-discovery
Finds and organizes TODO, FIXME, HACK, and NOTE comments in codebase. Use when user asks to "find TODOs", "show all FIXMEs", "list action items", or "what needs to be done".
Chokidarライブラリを中心としたファイルシステム監視の専門スキル。 Observer Patternによる効率的なファイル変更検知、クロスプラットフォーム対応、 EventEmitterによる疎結合な通知システムを設計・実装する。 Anchors: • Node.js EventEmitter / 適用: イベント駆動設計 / 目的: 疎結合な通知メカニズム • Chokidar Documentation / 適用: ファイル監視設定 / 目的: クロスプラットフォーム監視 • Observer Pattern (GoF) / 適用: イベント通知設計 / 目的: 変更検知と通知の分離 Trigger: Use when implementing file system watching, Chokidar configuration, file change detection, or event-based file monitoring systems. file watching, chokidar, fs watch, file change, event emitter, observer pattern, hot reload
Restructures existing code to improve readability, maintainability, and performance without changing external behavior. Trigger keywords: refactor, restructure, clean up, improve code, simplify, extract, modernize.
Play an alert sound and speak "Project NAME needs your attention." Use at the end of a run or whenever Codex needs user input or confirmation; derive the project name from the git remote (origin) with fallback to the repo folder or an override.
Migrates codex configuration files from v2.0 push-based sync to v3.0 pull-based retrieval format with automatic backups
Essential Git patterns for effective version control, eliminating redundant Git guidance per agent.
Plans and executes git commits with optional TICKET_ID prefix. Analyzes staged changes, proposes optimal commit structure (single or multiple), generates descriptive messages with technical context, and executes after user approval. Use when committing code changes, creating atomic commits, or splitting large changesets.
This skill should be used when the user asks to "analyze commits", "identify fix patterns", "detect code issues from commits", "git commit analysis", "parse commit history", or needs guidance on analyzing git commits to extract problem patterns and generate postmortem insights.
Mandatory audit workflow for UI/UX changes that reads current state FIRST, checks for redundancy, respects clean design philosophy, and identifies genuine gaps before implementation. Auto-invoked when user mentions UI, UX, design, layout, homepage, page improvements, visual changes, or interface modifications.
Git best practices, commit conventions, branching strategies, and pull request workflows. Use when working with git operations, commits, branches, or PRs.
Text manipulation and documentation engine. PRIMARY TOOL FOR TEXT EDITING. Use this skill for ALL text replacement, documentation updates, and file rewriting tasks. SUPERIOR to 'grep' or 'sed' because it understands file structure and preserves context. Safe for Markdown, Python, and Config files.
Expert documentation generator for coding projects. Analyzes codebases to create thorough, comprehensive documentation for developers and users. Supports incremental updates, multi-audience documentation, architecture decision records, and documentation health tracking. Works with any project type (APIs, CLIs, web apps, libraries). Use when you need to document a new project, update docs after adding features, or create comprehensive documentation for open source releases.
End-to-end release automation with semantic versioning, changelog generation, and multi-environment deployment
Dynamically validate codebase compliance with architectural decisions and constraints
Diagnose and fix Deptrac architectural violations automatically. Use when Deptrac reports dependency violations, layers are incorrectly coupled, or when refactoring code to respect hexagonal architecture boundaries. Never modifies deptrac.yaml - always fixes the code to match the architecture.
Cross-language architectural patterns for Go, Python, Bash, and Terraform. Covers dependency injection, error handling, configuration, logging, testing heuristics, and common anti-patterns. Use for architectural guidance and consistent patterns across languages. Triggers on "dependency injection", "DI pattern", "error handling pattern", "cross-language", "architectural pattern", "anti-pattern", "naming convention", "design pattern", "testing heuristic", "config pattern", "logging pattern".
Comprehensive guidance on setting up npm libraries with package.json, with a preference for ES Modules (ESM). Use when setting up npm packages, configuring ESM, TypeScript packages, or React component libraries.
Storybook integration with spec.md. Auto-generates Stories from Component API. Triggers: storybook, stories, component api, props, argTypes, variants, csf3.