review
Review project files for consistency, completeness, and correctness. Use when asked to review, audit, check, or validate project configuration files (justfile, Makefile, CI workflows, pre-commit config, pyproject.toml, Dockerfile, docker-compose, etc.) or documentation files (README, CLAUDE.md, CONTRIBUTING, etc.). Supports both single-file review and cross-file consistency checks.
What this skill does
# Project File Review Review project files across three dimensions, then suggest fixes and improvements. ## Dimensions - **Consistency**: Naming conventions, formatting, patterns, and style are uniform within and across files. - **Completeness**: Nothing is missing. All referenced targets, commands, variables, and dependencies exist. All expected sections are present. - **Correctness**: Syntax is valid. Commands work. Paths exist. Versions are compatible. Logic is sound. ## Workflow ### Phase 1: Individual File Review Review each file separately. For each file: 1. Read the file fully. 2. Evaluate against all three dimensions. 3. Report findings grouped by dimension. 4. Suggest specific fixes with code snippets. ### Phase 2: Cross-File Consistency When multiple files are provided, or after individual reviews, check alignment across files: 1. Verify shared references match (e.g., target names in justfile match CI workflow steps, Python version in pyproject.toml matches CI matrix and Dockerfile). 2. Check that documented commands in README match actual targets/scripts. 3. Confirm dependency lists are synchronized (e.g., pyproject.toml vs requirements files vs CI install steps). 4. Ensure CLAUDE.md reflects the actual project structure and tooling. ### Discovery Mode When reviewing a file, suggest other project files that should be cross-checked. Common relationships: - **justfile / Makefile** <-> CI workflows, README, pre-commit config - **pyproject.toml** <-> Dockerfile, CI workflows, pre-commit config - **README** <-> CLAUDE.md, justfile, CI workflows - **Dockerfile** <-> docker-compose, CI workflows, pyproject.toml - **pre-commit config** <-> CI workflows, pyproject.toml Offer to review related files the user hasn't mentioned yet. ## Output Format For each file, report: ``` ### <filename> #### Consistency - [finding + suggested fix] #### Completeness - [finding + suggested fix] #### Correctness - [finding + suggested fix] ``` After all individual reviews, add a cross-file section: ``` ### Cross-File Alignment - [inconsistency + which files + suggested fix] ``` Omit empty sections. Prioritize actionable findings over nitpicks.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.