Documentation

Docs, README files, API references, tutorials, specs, and changelogs

skills in category: 15,592
pages available: 650

Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.

Open in full browser

Browse documentation skills

Showing 3,073–3,096 of 15,592 skills

Lint ElispAFix byte-compile warnings, checkdoc notes, and other Elisp diagnostics in one or more files. Use when the user says "lint elisp", "fix warnings", "fix diagnostics", "elisp lint", "checkdoc", "byte-compile warnings", or wants to clean up Elisp compiler/linter output.documentationgoexpressVotes: 0GitHub stars: 12
Elisp ConventionsAApply local coding and verification rules when modifying or testing Emacs Lisp, or when explicitly reviewing code against these conventions. Use for dotfiles extras, standalone Elpaca packages, and other .el files; not for non-Elisp work or read-only bug, security, or design reviews where these conventions are not material.documentationbashexpressVotes: 0GitHub stars: 12
Add To Emacs PackagesAAdd or register one of the user's Emacs packages in my-emacs-packages.org, create its documentation note, and add its GitHub profile README card. Use when the user wants to update the public Emacs packages list for a specific package.documentationgoshellVotes: 0GitHub stars: 12
Org Note ConventionsAUse when creating or editing private or personal Org notes, regardless of directory; not package manuals, project documentation, READMEs, literate configuration, or other separately governed Org files.documentationgodocumentationVotes: 0GitHub stars: 12
Lint ElispAFix byte-compile warnings, checkdoc notes, and other Elisp diagnostics in one or more files. Use when the user says "lint elisp", "fix warnings", "fix diagnostics", "elisp lint", "checkdoc", "byte-compile warnings", or wants to clean up Elisp compiler/linter output.documentationgoexpressVotes: 0GitHub stars: 12
Generate ReadmeAGenerate or update a GitHub-facing README.md for an Emacs Lisp package from its Org manual. Use when the user says "generate readme", "create readme", "update readme", "readme from manual", or wants a concise Markdown README for an Elisp package. Do not use for general project README writing or for packages without an Org manual; use document-elisp-package first when the manual is missing.documentationnodegitVotes: 0GitHub stars: 12
Skills DirectorySkills Directory 3 slots · $399/mo · one ad per page · sponsors can never buy grades.See placements
Elisp ConventionsAApply local coding and verification rules when modifying or testing Emacs Lisp, or when explicitly reviewing code against these conventions. Use for dotfiles extras, standalone Elpaca packages, and other .el files; not for non-Elisp work or read-only bug, security, or design reviews where these conventions are not material.documentationbashexpressVotes: 0GitHub stars: 12
Document Elisp PackageACreate or update an Org manual for an Emacs Lisp package in the Denote manual style. Use for documenting Elisp packages or emacs/extras; use generate-readme for Markdown README generation alone.documentationgoshellVotes: 0GitHub stars: 12
Document Elisp ExtrasAAudit, create, or refresh documentation for all Emacs extras packages in the dotfiles repo. Use when the user asks to document every extras package, fill missing extras docs, refresh outdated extras docs, check extras documentation coverage, or bring emacs/extras/doc up to date with emacs/extras sources.documentationnodeexpressVotes: 0GitHub stars: 12
Add To Emacs PackagesAAdd or register one of the user's Emacs packages in my-emacs-packages.org, create its documentation note, and add its GitHub profile README card. Use when the user wants to update the public Emacs packages list for a specific package.documentationgoshellVotes: 0GitHub stars: 12
Tech DesignADraft, review, pressure-test, compare, and polish technical design documents for product, API, SDK, infrastructure, storage, migration, reliability, security, privacy, performance, data model, or architecture work. Use when an engineer wants to make and defend a technical decision, turn rough notes into a review-ready TD, review an existing TD, compare alternatives, or plan rollout/testing/migration/rollback for a proposed technical change.documentationgotestingVotes: 0GitHub stars: 3
SlackAWrite a message as a ready-to-paste Slack message, in nvie's own casual voice, using Slack-flavored markdown that formats correctly when pasted into the Slack composer and toggled with cmd+shift+f. Use when the user runs /slack, or asks to "write this as a Slack message", "slackify this", "draft a Slack message", or "post this in Slack". Output is the message text and nothing else -- no preamble, no explanation, no follow-up questions.documentationgodebuggingVotes: 0GitHub stars: 3
Quick ExplainerAPrime the brain for a context switch with one concrete example. Point at a PR, a tech design, a plan, a Mikado graph, an issue, a screenshot, or the current branch, and get back a sub-terminal-window explainer built entirely out of a single worked example: what goes wrong today, and what the same situation looks like once the change lands. Use when the user runs /quick-explainer, or asks to "catch me up on", "remind me what this is about", "what is this PR actually solving", or "explain this ...documentationgonodeVotes: 0GitHub stars: 3
Pyperformance Result CompareAUse when 比较已有 pyperformance run.json 或 speedup.json，判断收益、回归与噪声；不启动跑分。documentationpythonperformanceVotes: 0GitHub stars: 2
Isa Instruction LookupAUse when 查证 A64/x86 指令语义、编码、操作数或 feature 依赖，检索替代指令与跨平台等价候选。documentationgoVotes: 0GitHub stars: 2
Design DocumentationAUse when 编写或修改特性 RFC、架构、系统、功能或详细设计说明书；普通实验报告用 cinderx-optimization-report。documentationdocumentationVotes: 0GitHub stars: 2
Compiler Optimization TheoryAUse when 解释或评估 CinderX 的 IR、优化 pass、指令调度与寄存器分配原理；指令规格用 isa-instruction-lookup。documentationgoVotes: 0GitHub stars: 2
Cinderx Optimization ReportAUse when 将 CPython/CinderX 实验的环境、证据链、根因和回归结果整理成报告。documentationpythonVotes: 0GitHub stars: 2
Cinderx Jit Entry CheckAUse when 核实 benchmark 本体是否进入 CinderX JIT，排除启动期和第三方编译干扰。documentationpythonperformanceVotes: 0GitHub stars: 2
Cinderx Hir DumpAUse when 在真实 pyperformance worker 上采集 CinderX HIR 或 jit.log。documentationpythonperformanceVotes: 0GitHub stars: 2
Doc SyncASynchronize documentation with the current codebase. Fix drift between docs/prd.md, docs/system-design.md, and actual source code.documentationjavabashVotes: 0GitHub stars: 15
Prd AuthoringAPRD format conventions, boundary rules, and template references. Load when writing or reviewing product requirements.documentationpythongoVotes: 0GitHub stars: 15
DoctorADeterministic, blocking validation of the project's docs/ brief against the harness-project API: roster existence, required sections, data slots, naming conventions, channel invariants, and the reviewer roster. Load when onboarding a project, after a harness upgrade, or before starting pipeline work. Model-free, CI-runnable.documentationpythonbashVotes: 0GitHub stars: 15
Adr TemplateAArchitecture Decision Record format, naming conventions, and when to create ADRs. Load when making or documenting architectural decisions.documentationgogitVotes: 0GitHub stars: 15