config-file-explainer
Explain a configuration file and its key options. Use when a junior developer is confused by a config file.
Discover Tools skills, compare source repositories and read the instructions for each workflow.
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.
Explain lint errors and propose fixes. Use when a junior developer needs help resolving common lint or format warnings.
Create a minimal, repeatable reproduction plan for a bug. Use when a junior developer needs clear steps to reproduce and capture evidence.
Suggest small refactors that improve readability without changing behavior. Use when a junior developer asks to clean up code.
Define engineering standards across teams. Use when a senior developer needs to align practices.
Guide collection and analysis of performance traces. Use when a mid-level developer needs to diagnose slowness.
Harden configuration and defaults for safer deployment. Use when a mid-level developer needs to reduce misconfig risks.
Audit dependencies for licensing, security, and maintenance risk. Use when a senior developer needs risk assessment.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.