Zeljko Obrenovic
Community@zeljkoobrenovic · Amsterdam
Zeljko Obrenovic publishes Sokrates skills for evidence-based codebase analysis, covering architecture, security, performance, testing, and repository landscape configuration.
Agent Skills by Zeljko Obrenovic
Showing 25 vetted skills indexed across 1 GitHub repositories.
sokrates-features-of-interest
Defines and measures regex-based cross-cutting concerns for Sokrates repository analysis configurations.
sokrates-landscape-config
Creates and validates Sokrates landscape configurations aggregating multiple repository analyses into portfolio reports.
sokrates-virtual-landscapes
Designs and validates virtual landscape groupings for Sokrates repository analyses.
sokrates-decompositions
Designs logical component decompositions for Sokrates repository analyses and writes them into config.json.
sokrates-people-config
Merges duplicate contributor identities from git history into Sokrates config-people.json files.
sokrates-repo-config
Creates and validates Sokrates config.json files for repository source-code analysis.
evolution-scan
Narrates codebase evolution from Sokrates git history exports into eras, focus shifts, and trajectory findings.
storage-scan
Analyzes how a codebase stores, accesses, versions, and protects persistent data.
domain-language-scan
Extracts a codebase's domain vocabulary into a code-anchored glossary, context map, and drift report.
iac-scan
Analyzes infrastructure-as-code declarations to report provisioning coverage, environments, and hardening posture.
network-scan
Maps how a codebase connects over the network, including endpoints, protocols, TLS, proxies, and offline behavior.
configuration-scan
Analyzes how software is configured, tracing sources, precedence, defaults, secrets plumbing, and validation.
performance-scan
Statically reviews codebases for performance bottlenecks and produces ranked, evidence-backed findings.
architecture-scan
Infers a codebase's actual architecture from manifests, imports, and boundary contracts.
risk-synthesis-scan
Ranks Sokrates complexity, churn, and ownership metrics into explained, actionable code-risk findings.
full-scan
Orchestrates seventeen Sokrates codebase scanners in dependency order and merges validated findings.
observability-scan
Analyzes logging, metrics, tracing, and telemetry code to map a codebase's observability posture.
security-scan
Reviews codebase security design and audits code for injection, secrets, and crypto flaws.
maintainability-scan
Grades codebase maintainability across five sub-characteristics using Sokrates metrics and scanner findings.
tech-stack-scan
Inventories languages, frameworks, libraries, build tooling, CI/CD, and infrastructure with file/line evidence.
testing-scan
Analyzes a codebase's test suites to map coverage, quality, and gaps against Sokrates analysis data.
sokrates-scan-core
Defines the shared findings format, evidence rules, and validate/render/merge/diff scripts for Sokrates AI scanner skills.
cicd-scan
Reconstructs a codebase's CI/CD pipeline as an evidence-backed narrative of triggers, builds, gates, and releases.
reliability-scan
Analyzes error handling, failure isolation, recovery, and crash safety in a codebase.
Frequently Asked Questions About Zeljko Obrenovic
FAQPage SchemaWhat tasks can I accomplish with Zeljko Obrenovic's Sokrates skills?▼
You can run evidence-backed codebase scans covering tech stack, functionality, architecture, security, performance, reliability, testing, CI/CD, storage, network, configuration, and observability. Additional skills configure Sokrates repository analyses, logical decompositions, concern tracking, contributor merging, and multi-repository landscapes.
Who are these Sokrates skills designed for?▼
They target software engineers, architects, and technical leads who need to understand, audit, or document unfamiliar codebases. Typical users include teams doing due diligence, onboarding, technical-debt assessment, security review, or managing Sokrates reports across many repositories in an organization.
What are the prerequisites for running these scanner skills?▼
Most scanners work best with an existing Sokrates analysis (a _sokrates folder in the target project), and risk-synthesis, maintainability, evolution-scan, and full-scan require one. Several scanners, including tech-stack, storage, network, and configuration, degrade gracefully and still function without a prior Sokrates analysis.
How do the Sokrates configuration skills work in practice?▼
They create and tune _sokrates/config.json and landscape files, using proposal and preview scripts that measure candidate decompositions, concerns, and groupings against the real file tree. The scripts emit ready-to-paste configuration and validate scoping, contributor merges, and virtual landscapes before running the actual analysis.
How do the scanner skills ensure trustworthy findings?▼
All scanners follow the sokrates-scan-core foundation: a shared findings format with grouped results backed by file-and-line evidence, explicit evidence rules, and mandatory validate and render scripts. The full-scan skill runs scanners in dependency order, validates each, merges results, and diffs against previous runs.