Loading...
Loading...
Found 2,902 Skills
Sync ag-shared subrepo changes across ag-charts, ag-grid, and ag-studio repos
[Hyper] Create one or more Conventional Commits from the current repository state. Inspect staged and unstaged changes, group them into logical change sets, generate a compliant message per group, and commit each group separately in sequence.
Prepare a structured, scannable review checklist for a branch or diff, grouped by feature change and applying the four-pass review order (Types, Data Flow, Business Logic, Edge Cases) within each feature. Use when the user asks to "prep a review", "review order", or wants a checklist to manually walk through changes.
Self-directed iterative improvement system for Codex that cycles through modify, verify, retain/discard indefinitely
Review local code changes organized into logical chapters with Stage CLI, a code review tool that works with any AI agent
Run /test to write a test suite for code you just built or changed, after implementing a feature, route, or fix. Targets uncommitted changes automatically, reads test preferences.json for your framework (asks and saves it if absent), and picks the right strategy per file: happy path, edge cases, error states, accessibility.
Delegation mode for open-code-review (OCR). Instead of OCR calling an LLM endpoint, this skill instructs the host agent to perform the code review itself, using OCR only for deterministic engineering: file selection and rule resolution. Use when the host agent should drive the review with its own LLM capabilities.
Use when performing a standalone PR double-check in a clean context — review, fix, and post.
Use when performing a first-pass, read-only PR review in a clean isolated context.
Use when running the CTO flow-optimization loop — WIP scan, epic focus, triage unlabeled issues, and dispatch.
GitLab protected branch operations via API. ALWAYS use this skill when user wants to: (1) view branch protection rules, (2) protect/unprotect branches, (3) configure push/merge access levels, (4) set up code owner approval requirements.
Analyze how code changed over time. Use when investigating regressions, understanding why code was written a certain way, or finding when a behavior changed.