developerinlondon/code-quality
skills/code-quality/SKILL.md
Code quality standards: warnings-as-errors, no underscore prefixes for unused vars, mandatory test coverage. Apply to any TypeScript, JavaScript, Rust, or Python project. Triggers: code review, linting, writing new functions, refactoring.
development
Updated Apr 27, 2026
$ install --global
skillsauthnpx skillsauth add developerinlondon/agent-skills code-qualityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 4:34 AM415.3s1 file scanned
SKILL.md
- name:
- code-quality
- description:
- >-
- Code quality standards:
- warnings-as-errors, no underscore prefixes for unused vars,
- Triggers:
- code review, linting, writing new functions, refactoring.
Code Quality Standards
Unused Variables
- NEVER prefix unused variables with underscore (_) to silence linters
- Either USE the variable or REMOVE it entirely
- If a function parameter is required by an interface but unused, restructure to avoid it
- Exception: destructuring where you need to skip positional elements (rare)
Warnings Are Errors
- Treat ALL compiler/linter warnings as errors that must be fixed
- Do not leave warnings for "later" -- fix them now
- Common warnings to watch: unused imports, unreachable code, implicit any
Test Coverage
- Every new function or module MUST have corresponding tests
- Test the happy path AND at least one error/edge case
- Run existing tests after changes to verify nothing breaks
Type Safety
- Never use
as any,@ts-ignore, or@ts-expect-errorto suppress type errors - Never use empty catch blocks
catch(e) {} - Never delete failing tests to make the suite "pass"
Formatting
- Always run the project's formatter after editing any file
- Verify formatting before committing
Related Skills
developerinlondon/test-driven-development
development
VerifiedTrustedCommunity
Enforces strict Test-Driven Development (TDD) workflow: RED-GREEN-REFACTOR cycle. Tests MUST be written BEFORE implementation. Every change starts with a failing test. Applies to any language (Rust, TypeScript, Python, Go, etc.). Triggers: writing new features, fixing bugs, adding endpoints, refactoring, any code change.
SKILL.mdUpdated Apr 27, 2026
developerinlondon/project-planning
content-media
VerifiedTrustedCommunity
Structured project planning: break down a new project idea into plan files covering architecture, file structure, and implementation roadmap. Triggers: 'new project', 'plan a feature', 'break down', 'architecture', 'roadmap', 'design a system'.
SKILL.mdUpdated Apr 27, 2026
developerinlondon/issue-raiser
development
VerifiedTrustedCommunity
Raises well-structured GitLab issues with root cause analysis, proposed solutions, and correct assignees based on git history. Adapts to any GitLab instance and project conventions automatically. Triggers: raising issues, reporting bugs, creating tickets, filing defects, feature requests, refactoring proposals.
SKILL.mdUpdated Apr 27, 2026
developerinlondon/gitops-master
development
VerifiedTrustedCommunity
GitOps operations master for ArgoCD + Kargo. Diagnose stuck stages, verify deployments, manage promotions, configure verification and retry. Triggers: 'stage stuck', 'sync failed', 'promote', 'verify stage', 'kargo', 'argocd', 'gitops', 'pipeline', 'freight'
SKILL.mdUpdated Apr 27, 2026