MaTE Logo
MaTE Skills
SearchCollectionsCompareChangelogPricing
Agents:claude-codecodexcopilot
MaTE Skills — discovery, trust & activation for agent skills. Powered by Rainy MaTE
CollectionsSearchChangelogskills.sh

Comparison.

Evaluating clean-code vs pr-writer

Subject A
clean-code
Community
Subject B
pr-writer
Community
Decision Engine62% Confidence

clean-code

clean-code is the safer starting point, but both options need closer inspection.

clean-code has the stronger blended fit for this context.clean-code is safer or more trusted than pr-writer for the current team posture.Compatibility should still be validated in the target agent.
Score breakdown
clean-code
Trust95%
Safety95%
Freshness80%
Compat100%
pr-writer
Trust95%
Safety95%
Scenario Recommendations
Strict security environment
clean-code
clean-code has lower risk (0.05 vs 0.05) and fewer static signal flags.
Rapidly evolving projects
clean-code
clean-code has a higher freshness score (80%) indicating more recent maintenance.
Description
This skill embodies the principles of \"Clean Code\" by Robert C. Martin (Uncle Bob). Use it to transform \"code that works\" into \"code that is clean.\"
Create pull requests following Sentry's engineering practices.
Risk Evaluation
Low risk
Low risk
Trust Score
95%
Trust95%
95%
Trust95%

Deep Synthesis Engine

AI-powered deep comparison with scenario-based recommendations, trust analysis, and per-skill strengths. (2 credits)

Activation Vectors

clean-code
pr-writer
Freshness80%
Compat100%
Freshness Matrix
80%
Freshness80%
80%
Freshness80%
Security Signals
SignalAB
HTML comments✓✓
Remote exec✓✓
Network calls✓✓
Shell mutation✓✓
Sensitive files✓✓
Missing license✕✕
✓ = clean✕ = flagged
Both share: missing license. Installing either carries these signals.
Agent Compatibility
AGENTAB
claude-codeinferredinferred
codexinferredinferred
copilotinferredinferred
gemini-cliinferredinferred
cursorinferredinferred
windsurfinferredinferred
License Strictness
No License
No License
Optimal Context
Use this skill when: - **Writing new code**: To ensure high quality from the start. - **Reviewing Pull Requests**: To provide constructive, principle-based feedback. - **Refactoring legacy code**: To identify and remove code smells. - **Improving team standards**: To align on industry-standard best practices.
- You are ready to open a pull request and need a structured description based on the committed branch diff. - You want the PR body to capture what changed, why it changed, and any reviewer context. - You are using GitHub CLI and need a repeatable PR-writing workflow rather than writing the description ad hoc.