Nitra avatar

Nitra

Official

@nitra · Ukraine

0Followers
|
70Public Repos
|
10Published Skills

Nitra provides developer productivity skills for linting, documentation generation, dependency upgrades, mutation testing, and structured ideation.

Skills Distribution
DomainDeveloper To...Code Quality & Lin.. (30%)Documentation Gene.. (25%)Dependency & Versi.. (20%)Testing & Mutation.. (15%)

Agent Skills by Nitra

Showing 10 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About Nitra

FAQPage Schema
What tasks can I accomplish with Nitra's skills?

You can run delta linting on changed files, auto-generate Ukrainian markdown documentation per code file, upgrade project dependencies with major-change refactoring, iteratively write tests from surviving mutants, normalize ADR drafts in batches, prepare prompts for external agents, publish to a team Telegram channel, and run structured brainstorming sessions.

Who are Nitra's skills designed for?

They target software engineers and technical teams maintaining JavaScript/TypeScript, Vue, Python, and Rust codebases who need enforced lint hygiene, co-located documentation, safe dependency upgrades, and mutation-driven test coverage as mandatory steps in their task lifecycle.

How do the lint and coverage skills run in practice?

The lint skill executes npx @7n/rules lint against files changed versus origin, then fixes violations until a clean exit. The coverage skill runs npx @7n/test coverage, reads surviving mutants, and iteratively writes tests up to three iterations until convergence.

What are the prerequisites and dependencies for Nitra's skills?

Skills expect a git repository with an origin remote, Node.js with npx for @7n/rules and @7n/test, and optionally bun or npm, Cargo with cargo-edit for Rust crates, and uv for Python packages when pyproject.toml is present. Documentation output targets js/mjs/ts/vue/py files.

How does Nitra handle documentation freshness?

The doc-files skill generates concise behavioral Ukrainian markdown into a docs/ folder beside the code for every new or changed source file, orchestrated via JS, and verifies staleness using a CRC value stored in the document frontmatter.