debugging-checklist
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
Découvrez les skills Tests et sécurité, comparez leurs dépôts et consultez leurs instructions.
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.
Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.
Generate starter unit tests for a small function or module. Use when a junior developer needs test scaffolding and edge cases.
Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.
Design a multi-region architecture strategy. Use when a senior developer needs geo-redundant planning.
Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.
Explain a configuration file and its key options. Use when a junior developer is confused by a config file.
Review infrastructure-as-code changes for safety and correctness. Use when a mid-level developer needs a second look on IaC.
Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.
Recommend basic data structures for a task. Use when a junior developer needs help choosing lists, maps, or sets.
Design safe queue consumers and retries. Use when a mid-level developer needs reliable background processing.
Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.
Improve a README for clarity and completeness. Use when a junior developer needs guidance on documenting setup and usage.
Review a system architecture for scalability, reliability, and maintainability. Use when a senior developer needs to critique a design.
Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.
Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.
Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.
Assess and prioritize tech debt items. Use when a senior developer needs an investment plan for debt reduction.
Draft a basic SQL query from a simple requirement. Use when a junior developer needs help forming SELECT queries.
Review a pull request for correctness, regressions, and missing tests. Use when a mid-level developer needs structured review guidance.
Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.
Write concise docstrings for functions. Use when a junior developer needs help describing inputs, outputs, and errors.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.