Loading...
Loading...
Found 17 Skills
Review RFCs for problem clarity, compliance, security, and performance using SCQA framework
Assess SSOT integrity with intent-first methodology and produce conflict matrix with canonical source mapping.
Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.
Use when `spec.md`, `plan.md`, and `tasks.md` exist and you need a read-only Spec Kit audit for consistency, requirement-to-task coverage, ambiguity, duplication, or constitution conflicts before implementation.
One-stop skill for the project architecture center — draft new architecture documents, refresh existing ones, or conduct an architecture health check. Automatically determine the mode based on user input: `new` (draft)/ `update` (refresh to latest code status)/ `check` (review without modification, generate issue list). The `check` mode has three sub-objectives: consistency within a single feature design, alignment between design and code, and consistency among multiple documents under `codestable/architecture/`. Single-target rule — only modify one document or check one target at a time. Trigger scenarios: User says "fill in an architecture doc", "draft an architecture document", "refresh the architecture directory", "write down this module structure", "conduct an architecture check", "is the design internally consistent?", "does the plan match the code?", "are there conflicts among several documents in the architecture folder?", or when an architecture action is required before proceeding during the feature-design / feature-acceptance / implement phases.
Semantic content auditor (L3 Worker). Verifies document content matches stated SCOPE, aligns with project goals, and reflects actual codebase state. Called by ln-600 for each project document. Returns scope_alignment and fact_accuracy scores with findings.
Run /check-docs, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-docs instead if you want to fix issues immediately.
Use when auditing or fixing prose that reads like a leaked reasoning transcript — dead session citations, change narration, review residue, or hedged planning in docs, skill bodies, comments, or Agent Notes.
Checks hierarchy & links, SSOT, proactive compression, requirements compliance, freshness indicators, legacy cleanup, stack adaptation. Returns findings with severity, location, and recommendations.
Verify citations and references in scientific documents to detect hallucinated or invalid sources. Extracts DOIs, URLs, arXiv IDs, PubMed IDs, and ISBNs from Markdown, LaTeX, org-mode, and plain text, then validates them using API lookups and web fetches. Use this skill when: - Reviewing AI-generated content for citation accuracy - Validating references in papers, reports, or documentation - Checking if DOIs/URLs resolve to actual papers - Auditing a document for broken or fake citations
Comprehensive documentation audit and generation. Launches parallel agents for high-level docs, module-level docs, decision records, and state diagrams. Use when: documentation gaps, post-implementation docs, README updates, architecture docs.
Planner-pass coverage + redundancy report for an outline+mapping, producing `outline/coverage_report.md` and `outline/outline_state.jsonl`. **Trigger**: planner, dynamic outline, outline refinement, coverage report, 大纲迭代, 覆盖率报告. **Use when**: you have `outline/outline.yml` + `outline/mapping.tsv` and want a verifiable, NO-PROSE planner pass before writing. **Skip if**: you don't want any outline/mapping diagnostics (or you have a frozen/approved structure and will not change it). **Network**: none. **Guardrail**: NO PROSE; do not invent papers; only report coverage/reuse and propose structural actions as bullets.