Parse all `# implements:` annotations in source code and emit `library/_code-index.md` as a shelf-index. Also extracts cross-module import edges and writes `library/_dependency-edges.md`. Idempotent — re-running produces byte-identical output if no annotations or imports changed.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Use this skill to build or refresh the project's code index. The output is structurally a KB shelf-index, queryable by the research-librarian agent like the regular library files. Run after adding/changing # implements: annotations or modifying import structure.
Load the project root. Detect from .git/.
Walk source files. Glob **/*.{py,js,ts,go,rs,java} excluding standard ignored paths (.venv/, node_modules/, .git/, etc.).
Parse annotations. Use parse_code_annotations to extract every # implements: line.
Verify cited IDs. For each citation, look it up in library/_ids.md. Report unresolved citations as warnings (not errors — annotation_format_integrity blocks at pre-push).
Render the index. Use render_code_index to produce shelf-index-shaped markdown.
Write to library/_code-index.md. If the file already exists, compare byte-for-byte; only write if different.
Extract dependency edges. For each language detected in the project paths, invoke the registered DependencyExtractor adapter:
PythonAstExtractor (uses ast.parse for precise cross-module import resolution)GenericRegexExtractor (regex-based; configured per language via make_swift_extractor() or equivalent)Accumulate all returned ImportEdge objects across languages. Resolve each edge against the Decomposition module paths so edges carry qualified module IDs (e.g. P1.SP1.M1 → P1.SP1.M2). Edges that cannot be resolved to a known module are silently dropped (same policy as unresolved annotation citations).
Write to library/_dependency-edges.md. Use render_dependency_edges(edges, library_handle=<library-handle>) to produce the artefact. If the file already exists, compare byte-for-byte; only write if different. The file is consumed by visibility_rule_enforcement during decomposition validation.
Report. Print: number of annotations processed, number of unresolved citations, number of import edges extracted, whether either index file changed.
library/_code-index.md is up to date.library/_dependency-edges.md is up to date.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate a GitHub Actions workflow for Android — JDK + Gradle caching, build, unit + instrumented tests, Android Lint, run the Android pre-flight checks, and (optionally) sign + upload a signed app bundle to a Play track. Use when setting up CI for an Android app.
The English summary is being prepared. Showing the original description.
Validated Google Play release — runs the pre-flight checks and clears the Play policy gates, builds a signed app bundle with a git-stamped versionCode, uploads to a track, and walks staged rollout (with halt/roll-forward). Use when releasing an Android app to Play.
The English summary is being prepared. Showing the original description.
Scaffold a new Android app with SDLC and Play-safe defaults — Kotlin/Compose Gradle project with version catalog, convention plugins, module layout, a targetSdk that meets the Play mandate, R8 on release, and git-ignored signing so it passes the pre-flight checker from day one. Use when starting a new Android project.
The English summary is being prepared. Showing the original description.
Set up Android app signing safely — generate an upload keystore, enroll in Play App Signing, and wire a Gradle release signingConfig that reads secrets from a git-ignored keystore.properties / CI (never committed). Use when configuring signing for a Play release.
The English summary is being prepared. Showing the original description.
Pick an existing workflow for a task or author a new one — recommends workflow + team formation, or generates a fresh workflow YAML with command prompts and team validation.
The English summary is being prepared. Showing the original description.
Guide the team through writing a change-impact record for IEC 62304 / FDA / ISO 26262 ASIL C+ projects. Surfaces the affected REQ/DES/TEST/CODE artefacts and captures human-attested verification approach.
The English summary is being prepared. Showing the original description.