skills.rest
nitra
nitraOFFICIAL
Explore all skills by this author →
WebsiteGitHub

n-doc-files

Generates concise Ukrainian behavioral markdown documentation for changed code files.

Updated Jun 25, 2026
Search Tags:#documentation#markdown#monorepo#code documentation#ukrainian#crc#stale detection
One-click install
npx skills add https://github.com/nitra/7n-test --skill n-doc-files-nitra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n-doc-files
Source: https://github.com/nitra/7n-test/tree/main/.pi/skills/n-doc-files
Command: npx skills add https://github.com/nitra/7n-test --skill n-doc-files-nitra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping per-file documentation in sync with code is tedious and often skipped. This Skill makes documentation generation a mandatory, lint-like step: for every new or modified code file (js/mjs/ts/vue/py), it produces a concise behavioral markdown document in Ukrainian inside a docs/ folder next to the code. ## Core Features & Use Cases - Automated doc generation: Creates laconic Ukrainian markdown documentation describing the behavior of each changed or new code file. - Staleness detection via CRC: Stores a CRC checksum in the document frontmatter to detect when the source file has changed and the documentation is outdated. - JS-orchestrated workflow: Coordinates generation through JavaScript tooling, delegating detailed instructions to the referenced .cursor/skills/n-doc-files/SKILL.md. - Use Case: After modifying several TypeScript modules in a monorepo, run this Skill to regenerate docs/ markdown files for each changed module and flag any documents whose CRC no longer matches the source. ## Quick Start Generate or update Ukrainian markdown documentation in the docs/ folder for every code file I changed in this task.

Frequently Asked Questions about n-doc-files

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate documentation for changed code files?▼

Run this Skill as a mandatory step after modifying code. It generates a concise Ukrainian markdown document per changed file (js/mjs/ts/vue/py) and places it in a docs/ folder next to the source code.

How to detect outdated documentation when code changes?▼

The Skill stores a CRC checksum of the source file in the markdown frontmatter. When the file changes, the CRC no longer matches, marking the documentation as stale and triggering regeneration.

Which file types are supported for documentation generation?▼

Supported file types are JavaScript (.js, .mjs), TypeScript (.ts), Vue (.vue), and Python (.py). Each changed or new file of these types gets its own behavioral markdown document.

What language is the generated documentation written in?▼

The generated markdown documentation is written in Ukrainian and describes the behavior of the code file concisely. It is stored in a docs/ directory located next to the documented source code.

Where are the detailed instructions for this Skill defined?▼

The SKILL.md in this unit delegates execution to the instructions in .cursor/skills/n-doc-files/SKILL.md, which contains the full operational workflow for the documentation generation.

Related Skills

Explore More Software Engineering Skills→
CMiller838CMiller838

verification-loop

Runs build, type, lint, test, security, and diff checks to verify code changes before PRs.

Community
Intermediate
telagodtelagod
238

verify-change

Analyze workspace changes to detect documentation drift and missing tests.

Community
Intermediate
dalawwadalawwa

tdd:fix-tests

Orchestrate automated debugging and repair of failing tests after code changes.

Community
Advanced
patricio0312revpatricio0312rev
5

jsdoc-typescript-docs

Generate API documentation from JSDoc comments in TypeScript projects.

Community
Intermediate