Loading...
Loading...
Found 2,897 Skills
A clear, concise description of what this skill does (1-2 sentences). Focus on the VALUE it provides to the user.
Repository understanding and hierarchical codemap generation
Generate or update PROJECT_MAP.md for user-specified folders. Applicable to scenarios where users request directory maps/project maps/repository overviews/folder-level descriptions/updating existing PROJECT_MAP.md. Must first ask for the folder scope to scan, default full-repository scanning is prohibited; supports single directory or multiple directories (combined or generated separately).
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.
Manage project changelog following Keep a Changelog format. Use when documenting releases, adding change entries, generating changelogs from commits, or maintaining version history.
Top orchestrator for complete doc system. Delegates to ln-110 coordinator (project docs via 5 L3 workers) + ln-120-150 workers. Phase 4: global cleanup. Idempotent.
Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohes
Create an llms.txt file from scratch based on repository structure following the llms.txt specification at https://llmstxt.org/
Update a markdown file section with an index/table of files from a specified folder.
Use when asked to create a code walkthrough, explain how code works linearly, generate a walkthrough for a PR or codebase, or when user says /walkthrough. Triggers on "walkthrough", "explain the code", "how does this work", "walk me through".
Use only when explicitly asked to write or edit prose. Not for code comments, commit messages, or inline docs.
Refresh stale learning docs and pattern docs under docs/solutions/ by reviewing them against the current codebase, then updating, consolidating, replacing, or deleting the drifted ones. Trigger this skill when the user asks to refresh, audit, sweep, clean up, or consolidate stale docs in docs/solutions/ (phrases like "refresh my learnings", "audit docs/solutions/", "clean up stale learnings", "consolidate overlapping docs", "compound refresh", "/ce-compound-refresh"), or when ce-compound has just captured a new learning and flagged a specific older doc in docs/solutions/ as now inaccurate or superseded — invoke with the narrow scope hint ce-compound provides. Also trigger when the user points at a specific learning or pattern doc under docs/solutions/ and calls it stale, outdated, overlapping, or drifted. Do not trigger for general refactor, migration, debugging, or code-review work unless the user has explicitly directed attention to docs/solutions/ itself.