Lazare-Panam avatar

Lazare-Panam

Community

@Lazare-Panam

0Followers
|
5Public Repos
|
11Published Skills

Lazare-Panam provides software engineering discipline skills covering debugging, code review, CI/CD pipelines, security hardening, observability, and git versioning practices.

Skills Distribution
DomainDeveloper To...Code Quality & Rev.. (30%)CI/CD & Release En.. (20%)Security & Privacy.. (20%)Debugging & Observ.. (20%)

Agent Skills by Lazare-Panam

Showing 11 vetted skills indexed across 1 GitHub repositories.

Lazare-PanamLazare-Panam

debugging-and-error-recovery

Diagnose test failures, build errors, and runtime bugs through a structured root-cause triage checklist.

Community
Intermediate
Lazare-PanamLazare-Panam

planning-and-task-breakdown

Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.

Community
Intermediate
Lazare-PanamLazare-Panam

api-and-interface-design

Guides design of stable REST APIs, TypeScript interfaces, and module contracts.

Community
Intermediate
Lazare-PanamLazare-Panam

ci-cd-and-automation

Configures CI/CD pipelines with quality gates, deployment strategies, and rollback workflows.

Community
Intermediate
Lazare-PanamLazare-Panam

code-review-and-quality

Reviews code changes across correctness, readability, architecture, security, and performance before merge.

Community
Intermediate
Lazare-PanamLazare-Panam

security-and-hardening

Hardens web application code against OWASP vulnerabilities, SSRF, and LLM-specific attack surfaces.

Community
Advanced
Lazare-PanamLazare-Panam

observability-and-instrumentation

Instruments production code with structured logging, metrics, tracing, and alerting.

Community
Intermediate
Lazare-PanamLazare-Panam

interview-me

Extracts underlying user intent through one-question-at-a-time interviews until 95% confidence.

Community
Intermediate
Lazare-PanamLazare-Panam

code-simplification

Refactors code to reduce complexity while preserving exact behavior and project conventions.

Community
Intermediate
Lazare-PanamLazare-Panam

doubt-driven-development

Subjects non-trivial decisions to adversarial fresh-context review before they stand.

Community
Advanced
Lazare-PanamLazare-Panam

git-workflow-and-versioning

Structures git commits, branching, semantic versioning, and changelog practices for code changes.

Community
Intermediate

Frequently Asked Questions About Lazare-Panam

FAQPage Schema
What tasks can I accomplish using Lazare-Panam's skills?

You can perform root-cause debugging, break specs into ordered implementable tasks, design REST or GraphQL interfaces, set up CI/CD pipelines with quality gates, conduct multi-axis code reviews, harden code against vulnerabilities, add logging/metrics/tracing instrumentation, simplify complex code, and manage git branching, tagging, and semantic versioning.

Who are Lazare-Panam's skills designed for?

Software engineers and engineering teams shipping production code. The skills target developers reviewing changes before merge, handling untrusted input or personal data, operating production services needing observability, and anyone managing releases, parallel branches, or high-stakes decisions requiring adversarial verification.

How do the skills handle security and privacy requirements?

The security-and-hardening skill applies when handling user input, authentication, data storage, or third-party integrations. It explicitly covers features managing user sessions and personal data subject to GDPR and CCPA privacy compliance, hardening code against vulnerabilities before deployment.

When should I use the interview-me and doubt-driven-development skills?

Use interview-me when a request is underspecified, extracting true intent through one-question-at-a-time dialogue until roughly 95% confidence. Use doubt-driven-development when correctness outweighs speed: unfamiliar code, production or security-sensitive logic, and irreversible operations get adversarial fresh-context review.

What prerequisites or dependencies do these skills require?

No external dependencies are specified in the manifest. The skills are methodology-driven: they apply to existing contexts like failing tests, specs awaiting task breakdown, code pending review, production services needing instrumentation, and repositories requiring branching, tagging, or changelog management.