Use when you need to understand the Pyre or Pysa codebase architecture, find where specific functionality is implemented, or navigate the source directory structure. Use when working on OCaml code, debugging type checking or taint analysis issues, or exploring the codebase.
npx skills add https://github.com/facebook/pyre-check --skill architecture
client/): Reads .pyre_configuration, determines flags, shells out to pyre.binsource/main.ml): Routes to Check, Analyze (Pysa), Infer, Server, CodeNavigation, or NoDaemonQuerysource/menhir_parser/, source/cpython_parser/): Python source -> AST (source/ast/)source/analysis/): Populates global type environment in parallel. All sources added at once (not recursively following imports). Builds a layered environment chain: UnannotatedGlobalEnvironment -> ClassHierarchyEnvironment -> TypeAliasEnvironment -> AnnotatedGlobalEnvironment -> FunctionDefinitionEnvironment -> ErrorsEnvironment -> TypeEnvironmentsource/analysis/typeCheck.ml): Each function checked in parallel via control flow graph. Propagates parameter types through function body, checks compatibility at each operation. Never goes beyond function call boundaries.source/interprocedural_analyses/taint/taintAnalysis.ml): Main entrypoint of the analysis, runs the different analysis stepssource/interprocedural/pyrePysaApi.ml): Provides an API to query a type checker (pyre or pyrefly)source/interprocedural/classHierarchyGraph.ml): Builds a class hierarchy graphsource/interprocedural/callablesSharedMemory.ml): Builds a mapping from callables (functions and methods) to their AST and signaturesource/interprocedural/callGraph.ml): Defines call graph data structuressource/interprocedural/callGraphBuilder.ml): Builds call graphs for all callablessource/interprocedural_analyses/taint/modelParser.ml): Parses .pysa model filessource/interprocedural_analyses/taint/forwardAnalysis.ml): Tracks taint from sourcessource/interprocedural_analyses/taint/backwardAnalysis.ml): Tracks taint to sinkssource/interprocedural_analyses/taint/taintConfiguration.ml): Defines rules connecting sources to sinkssource/interprocedural/fixpointAnalysis.ml): Implements a global fixpoint over callablessource/interprocedural_analyses/taint/model.ml): Defines a summary of the taint behavior of a function, inferred during analysissource/ast/: Python AST representation (Expression, Statement, Source, Location, Reference)source/analysis/: Core type checker: type representation (type.ml), CFG, fixpoint, preprocessing, environments, type order, class hierarchysource/interprocedural/: Interprocedural framework: call graph, dependency graph, override graph, fixpointsource/interprocedural_analyses/taint/: Pysa taint analysis: sources, sinks, domains, models, rules, reportingsource/interprocedural_analyses/type_inference/: Interprocedural type inferencesource/server/: Pyre daemon for incremental analysissource/code_navigation_server/: IDE code navigation serversource/command/: OCaml CLI command implementationssource/buck_command/: Buck-specific commandssource/buck_integration/: Buck build system integrationsource/service/: Shared memory management, schedulingsource/domains/: Abstract domain library (lattices for interprocedural analyses)source/hack_parallel/: Shared memory and multi-worker infrastructure (forked from Hack)source/saved_state/: Serialization for incremental analysisclient/: Python CLI (pyre command)client/commands/: All user-facing commands (check, analyze, start, stop, infer, query, etc.)client/configuration/: .pyre_configuration file parsingclient/language_server/: LSP protocol implementationapi/: Programmatic Python API for Pyre serverpyre_extensions/: Runtime Python helpers (none_throws, safe_cast, etc.)tools/generate_taint_models/: Auto-generation of Pysa taint modelstools/typeshed_patcher/: Applies patches to bundled typeshed stubsstubs/: Bundled typeshed with patching mechanismfacebook/: Meta-internal code (not open-sourced)show, eq, compare, to_yojson via PPX derivers. For a type Module.t, Module.show gives a debug string.Log.dump "format %s" value and run with pyre --noninteractive checkpyre_dump(), pyre_dump_cfg(), pyre_dump_locations(), and reveal_type(x) to inspect Pyre's stateGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Take facebook/architecture from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.