Total 38,612 skills
Showing 12 of 38612 skills
Show current loop state. TRIGGERS - ru status, loop status, autonomous status, check ru state.
Orchestrates a structured design review by running existing skills in a diagnostic funnel, from complexity triage through structural, interface, and surface checks to a full red-flags sweep. Use when reviewing a file, module or PR for overall design quality and you want a comprehensive, prioritized assessment rather than a single-lens check. Not for applying one specific lens (use that skill directly) or for evolutionary analysis of how code changed over time (use code-evolution).
Complete development with structured merge/PR options. Use when ready to merge or submit work.
Create a PR for the current branch. Use when the user asks to create a pull request, submit PR, or says 'pr'.
Create or configure a fork workflow with git-town. Preflight checks at every step. TRIGGERS - fork repo, setup fork, git-town fork, create fork, fork workflow, upstream setup.
Find orphan functions, dangling imports, and dead code via GitNexus CLI (npx gitnexus@latest). CLI ONLY - NO MCP server exists, never use readMcpResource with gitnexus:// URIs. TRIGGERS - dead code, orphan functions, unused imports, dangling references, unreachable code.
Create and improve OpenAkita skills. It is used when you need to: (1) create new skills for repetitive tasks, (2) improve existing skills, (3) encapsulate temporary scripts into reusable skills. Skills are the core mechanism of OpenAkita's self-evolution.
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step. TRIGGERS - contribute, feature branch, create PR, submit PR, git-town contribute.
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
Use this skill when spreadsheet files are the primary input or output. This means the user wants to: open, read, edit, or repair existing .xlsx, .xlsm, .csv, or .tsv files (e.g., add columns, calculate formulas, format, create charts, clean messy data); create new spreadsheets from scratch or from other data sources; or convert between spreadsheet file formats. Trigger this especially when the user references a spreadsheet file by name or path—even casually (such as "the xlsx in my downloads")—and wants to process it or generate content from it. It's also used to clean or reorganize messy tabular data files (rows with incorrect formatting, misaligned headers, garbage data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do not trigger this when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
Testing doctrine, commands, and test layout conventions
Run integration tests for component interactions