Análisis de documentación: evalúa la cobertura, detecta desviaciones entre código y documentación con reconciliación de planes, y visualiza dependencias con el gráfico de documentos. Responde '¿qué necesita documentación?' y '¿sigue siendo precisa la documentación?'
Esta habilidad de agente de IA está diseñada para analizar y mantener la calidad de la documentación técnica. Permite evaluar la cobertura documental, identificando áreas del código que carecen de documentación adecuada. Además, detecta desviaciones entre el código fuente y su documentación correspondiente, utilizando un mecanismo de reconciliación de planes para garantizar la precisión. Visualiza las dependencias entre documentos mediante un gráfico de documentos, lo que facilita la comprensión de la estructura y las relaciones. Es compatible con plataformas como Claude Code y Cursor, y su funcionamiento se basa en el análisis de archivos de documentación y código fuente, ofreciendo respuestas claras a preguntas clave sobre el estado de la documentación.
npx skills add https://github.com/trkbt10/indexion-skills/tree/main/skills/indexion-documentationInstalled? Explore more Investigación y análisis de datos skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
Análisis de documentación: evalúa la cobertura, detecta desviaciones entre código y documentación con reconciliación de planes, y visualiza dependencias con el gráfico de documentos. Responde '¿qué necesita documentación?' y '¿sigue siendo precisa la documentación?'
This repo contains 8 individual skills — each has its own dedicated page.
Generate and use a pre-edit structure brief so coding agents learn likely owners, consumer surfaces, and unsafe edit locations before implementing.
Detect and review name/content drift in code using `indexion identity audit`, then plan verified renames, moves, folder changes, or splits.
Debug and inspect KGF specs — view tokenization results, parse trees, and extracted edges from source files. Use when adding/fixing language support or when indexion's analysis output looks wrong.
README construction — initialize template structure, generate per-package READMEs from doc comments, plan writing tasks, assemble root README from docs/ and package READMEs via doc.json config, and verify edits with `plan drift`.
After writing code, detect and clean up duplication at three levels — copy-paste blocks, cross-package shared code, unnecessary wrappers, and concept-level SoT violations. Detect with indexion, fix, and verify.
Generate SDD requirements from RFCs/specs and quantitatively verify implementation conformance. spec draft → spec align → spec verify → automated validation loop with codex/claude. Operate spec-to-impl drift gates as CI checks.
Split text into contextual chunks for RAG/embedding pipelines. Document segmentation and section extraction using window, tfidf, punctuation, or hybrid strategies chosen by intent.
Project wiki lifecycle — create pages, track source changes with ingest, update stale pages, lint structural integrity, detect code-to-doc drift with reconcile, and manage search indexes. A runbook for navigating and maintaining the wiki as an agent.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.