project_culture_skill

Overview

This skill evaluates code maturity and project culture against MultiversX standards to estimate reliability and audit priorities. It highlights documentation completeness, testing culture, code hygiene, and dependency management to produce actionable signals for developers and auditors. The goal is to quickly surface strengths and red flags so teams can prioritize fixes and reviewers can focus where risk is highest.

How this skill works

The skill inspects repository artifacts and CI scripts to detect presence and quality of documentation, build/deploy helpers, and formal specs. It examines test suites (unit, integration/Mandos scenarios, and simulator usage), linting results, unsafe patterns (magic numbers, unwraps), and dependency pinning/lockfile behavior. From these checks it synthesizes a maturity level and recommends audit focus areas.

When to use it

• Before a security audit to scope effort and identify risky areas
• During code review to enforce testing and documentation standards
• When preparing a release to verify stability and repeatable builds
• Onboarding new contributors to map project conventions and gaps
• Periodic health checks to track technical debt and culture improvements

Best practices

• Maintain clear build and test instructions and include deploy/interaction scripts for reproducible runs
• Strive for Mandos/integration scenario coverage for every public endpoint; include simulator runs in CI
• Run and fix linter complaints; replace magic numbers with named constants and reduce unchecked unwraps
• Commit a lockfile and pin critical dependencies to avoid surprising upgrades
• Document specs and design decisions in a dedicated specs or whitepaper folder

Example use cases

• Assess a smart contract project to decide whether to hire an external auditor or run internal tests first
• Prioritize remediation tasks after a preliminary scan flags missing tests and unpinned dependencies
• Guide continuous integration setup by identifying missing simulator or scenario steps
• Provide a checklist for maintainers to raise project maturity before token launches or audits