Netcracker Technology
Official@netcracker · Boston, MA
Netcracker engineers' open source projects
Agent Skills by Netcracker Technology
Showing 15 vetted skills indexed across 2 GitHub repositories.
envgene-bdd-tests
Creates and verifies Gherkin/Cucumber BDD tests for the EnvGene environment generator.
dev-flow
Orchestrates design-to-PR delivery as isolated phase subagents with per-phase model routing.
design-to-cr
Drafts, validates, and files change request issues in Netcracker/qubership-envgene from settled designs.
writing-docs
Enforces house style rules when writing or editing Markdown documentation and prose.
behavioral-guidelines
Enforces disciplined coding principles for planning, implementing, and testing changes in this repository.
discrepancy-audit
Audits EnvGene documentation against code and schemas to produce a verdict table of discrepancies.
writing-gherkin
Generate acceptance criteria and Cucumber Gherkin scenarios from feature docs, topics, or change requests.
writing-adrs
Write terse one-page Architecture Decision Records in Nygard format under docs/adr.
bdd-test-review
Reviews pytest-bdd Gherkin scenarios and test data in pull requests for completeness and validity.
markdown
Audit Markdown files for markdownlint violations and fix them in-place.
pull-request
Generate PR titles and bodies compliant with project conventions using gh CLI.
doc-update
Generate and synchronize GitHub Actions documentation from action.yml changes.
sync-docs
Scan recent git commits to update documentation for changed actions and workflows.
zizmor
Audit GitHub Actions workflows and action.yml files for security issues and apply automated fixes.
preflight
Audit changed Markdown and GitHub workflow files for markdownlint and zizmor violations, fix them in place, and commit.
Frequently Asked Questions About Netcracker Technology
FAQPage SchemaWhat specific repository maintenance tasks do these utilities perform?▼
These utilities perform automated auditing and remediation of Markdown files, synchronize documentation based on configuration changes, enforce pull request title conventions, and scan repository configuration files for security vulnerabilities. They ensure repository health by fixing identified violations directly within the codebase.
Which engineering personas benefit from these repository utilities?▼
DevOps engineers, technical writers, and repository maintainers benefit from these utilities. They are designed for teams managing large-scale GitHub environments who require consistent documentation, strict security posture for configuration files, and standardized contribution metadata across multiple repositories.
What are the primary dependencies for running these repository utilities?▼
These utilities require a standard Git environment and access to the GitHub ecosystem. They rely on specific linting standards for Markdown and security analysis patterns for configuration files. Users must have appropriate repository permissions to commit changes directly to the codebase during the remediation process.