Coding standards, frameworks, refactoring, and code review (18.6K skills)
Use this skill to organize everyday Git work, from creating branches and writing focused commits to opening pull requests and resolving conflicts. It includes workflow and naming examples, commit conventions, PR checklists, and commands for correcting or reviewing history.
Build a new external service integration as a packaged Python CLI. The skill guides the project layout, API client, command-line interface, credential declarations, health check, and tests so the tool can be installed and used by agents.
Prepare repository changes for review by creating a named branch, committing with a Conventional Commit message, pushing it, and opening a GitHub pull request. The workflow also covers adding required attribution and returning the PR link.
Develop and debug Centaur harness-server backends: add harness CLIs, normalize their output into the shared protocol, and investigate streaming, interrupts, session resume, model selection, and reasoning controls across supported harnesses.
Apply Disney’s 12 animation principles to code-driven motion in interfaces, web scenes, games, and 3D projects. Diagnose why movement feels stiff or unclear, then plan readable poses, timing, and secondary motion with deterministic frame-based behavior.
Reviews an iOS or macOS Xcode project and App Store metadata for common rejection risks across privacy, subscriptions, design, entitlements, and more. It produces findings by severity with suggested fixes, then supports rechecking issues after changes.
Scan a React codebase for potential security, performance, correctness, and architecture issues. The skill reports a 0–100 health score and findings with affected files and line numbers, giving developers leads to verify against the app's actual behavior.
Maintain a project's Changelog using evidence from its repository. Decide which changes deserve an entry, draft or publish supported updates, prepare release notes, validate generated files, and reconstruct missing historical entries without inventing dates or delivery claims.
Check documentation health when finishing a feature or cleaning up the `developing/` docs. The skill runs the repository’s documentation lifecycle verifier and applies README deletion rules defined by the project’s documentation guide.
Use this skill to decide whether an OpenMeld change belongs in the Changelog, draft or publish an entry, prepare release notes, check generated Changelog views, or fill in missing historical changes.
Plan and implement OpenMeld business data storage on PostgreSQL, including schemas, migrations, transactions, Hyperdrive connections, and data cutover. Use it to guide PostgreSQL work within the existing architecture, with checks for migration state, ownership, and affected consumers.
Start investigating a Wake that failed, stalled, or produced no visible reply. The skill directs the agent to the service trace command and the architecture documents that define execution evidence and diagnostic boundaries.
Capture two web pages or image files for a visual comparison. Choose a page element with a CSS selector, set a mobile, tablet, or custom viewport, and create a Markdown comparison for PRs when needed.
Run the existing `greploop` workflow with the `@greptile-apps` trigger when the usual trigger cannot handle a large pull request. This entrypoint depends on the separate `greploop` skill and adds no workflow of its own.
Prepare an isolated Git worktree and branch for each feature, fix, or documentation task. Check for an existing assignment and overlapping pull requests first, so edits stay scoped to the right work and do not build on another task’s changes.
Use this guide to decide when repeated operational code should become a shared service, while keeping product rules in the workflow actions that own them. It provides practical design principles and a gradual migration checklist to preserve existing boundaries and behavior.
Review Greptile feedback on a pull request, merge request, or shelved changelist, then make scoped fixes and request fresh reviews within a set cycle limit. Track actionable findings and report the current score, checks, and any work left unresolved.
Inspect tables and query rows in a Supabase Postgres database through PostgREST, then insert, update, or delete records. Changes require an exact confirmation, and updates or deletes must include an equality filter to target rows. Useful for checking or maintaining project data.
Review Sentry organizations, projects, and frequent unresolved issues from the past 24 hours. Triage errors by resolving, archiving, or assigning issues to a user or team.
Use this skill to check the connected GitLab account, list its projects, review a project's open merge requests, and create an issue with a title and description in a chosen project.
Check the connected GitHub profile, list repositories, and view open issues in a repository. It can also create an issue with a supplied title and body after the repository and issue details are confirmed.
Check whether a Framer project’s Server API credentials work by performing the official connection handshake. The skill verifies the project and API key pair and reports connection details such as the active branch.
Turn approved requirements for a substantial, multi-step workstream into a bounded implementation plan. Map owners and files, define compatibility and verification, break the work into executable tasks, and select an appropriate execution route before code changes begin.
Use this skill when a project needs a shared, consistent vocabulary. It checks terminology against approved decisions, code, and tests, then updates the relevant CONTEXT.md for resolved facts or identifies ambiguity that needs a user decision.