handler-sync-github
GitHub-specific sync mechanism - file copying, pattern matching, and safety checks
Essential command-line tools and system utilities.
GitHub-specific sync mechanism - file copying, pattern matching, and safety checks
Run focused `kit` CLI commands (file-tree, symbols, search, semantic discovery, dependency analysis, and exports) to build high-signal repository context fast. Use when you need to understand an unfamiliar codebase, prep context for Claude, plan refactors, audit dependencies, or answer “where is X implemented?” without manually grepping.
Generate commit messages following the DAFT convention, which requires exactly one letter as the commit message. Use this skill when creating commits, suggesting commit messages, or validating commit message format.
Apply Progressive Disclosure principles to organize large documentation projects. Restructure docs into hierarchical structure, reduce token usage by 95%+, and create README files for navigation.
Git version control operations including status, branches, commits, diffs, and worktree management. Use when working with git repositories, reviewing changes, or managing branches.
Log file analysis including reading, searching, filtering, and pattern matching. Use when investigating issues in logs, searching for errors, or analyzing application behavior.
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?"
Manage your personal knowledge base of curated resources, bookmarks, and excerpts. Triggers include "knowledge base", "kb", "add to knowledge", "add tabs to", "what do I have on", "what do we know about", "find resources about". Use with safari-tabs skill for bulk ingestion from Safari windows. Location is ~/knowledge/.
Store important information, decisions, implementations, or learnings to the knowledge base. Use when preserving context, decisions, debugging solutions, or implementation details for future reference.
Sync existing steering documents from workspace .kiro/steering/ to knowledge base with Context sections. Use when steering docs already exist and need syncing to knowledge base.
Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content
Document REST APIs with OpenAPI/Swagger specifications, endpoint documentation, authentication, error handling, and SDK guides. Use for API reference docs, Swagger specs, and client library documentation. Triggers: api docs, openapi, swagger, endpoint documentation, rest api, api reference, sdk documentation, api specification, document api, api endpoints.
Explain how code/features work by tracing execution flow. Saves markdown to ~/Developer/explanations/ and previews in browser.
Generate navigable code maps for unfamiliar codebases. Use when exploring a new codebase, needing to understand project structure, or before diving into code modifications. Extracts exports/imports via AST (tree-sitter) to create _MAP.md files per directory. Triggers on "map this codebase", "understand this project structure", "generate code map", or when starting work on an unfamiliar repository.
Working with .autodoc/ directory, automatic documentation generation, semantic doc search
Professional malware analysis report creation for enterprise malware analysis and incident response. Use when the user needs to create, structure, or improve a malware analysis report, write technical documentation for malware samples, create executive summaries, or format IOCs and detection rules for professional delivery.
Review code diffs for bugs, edge cases, state issues, and consequences. Provide prioritized findings with specific fixes.
Detects when high-level project documentation is stale based on code/config changes and generates update suggestions
Code quality automation for linting and formatting. Provides ESLint, Prettier, Biome setup, CI/CD integration, pre-commit hooks, and tool migration strategies for consistent code style enforcement. Anchors: • ESLint Official Docs / Apply: Rule configuration, plugin integration / Purpose: Correct API usage and best practices • Prettier Philosophy / Apply: Opinionated formatting / Purpose: Minimize configuration bikeshedding • Biome Performance Model / Apply: Rust-based tooling / Purpose: Optimize development workflow speed Trigger: Use when setting up linting/formatting for new projects, integrating code quality into CI/CD, configuring pre-commit hooks, or migrating between tools. eslint, prettier, biome, lint, format, pre-commit, husky, lint-staged, code quality
Systematically explore codebases using search and LSP to understand code structure, intent, and behavior. READ_ONLY mode - no file modifications.
Security fix patterns for configuration and deployment vulnerabilities (path traversal, debug mode, security headers). Provides language-specific secure implementations.
Setup ESLint with Airbnb TypeScript config and Prettier formatter for code quality enforcement. Use when setting up new project, adding linting/formatting, or configuring code quality tools (e.g., "Setup ESLint and Prettier", "Configure code quality", "Add Airbnb linter").