fable-native-code
De la autor
Use when writing or editing code in an existing codebase — before adding comments, docstrings, try/catch blocks, validation, logging, or TODOs the surrounding file doesn't have, and before explaining your style choices in the reply.
Instalare
npx skills add DizzyMii/fable-skills --skill fable-native-code -a claude-code
Se instalează în .claude/skills/fable-native-code/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 82
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- fable-prove-itDizzyMii/fable-skillsUse before claiming anything works, is fixed, is done, or passes; before status updates on changes you haven't run; before agreeing with someone else's claim about your work; and before state-changing commands like restarts, deletes, or config edits.Redactare★ 56
- fable-scope-disciplineDizzyMii/fable-skillsUse when implementing any change in existing code — when tempted to clean up nearby code, add unrequested validation or options, fix something "arguably in scope", or when the diff is growing past what was asked.Inginerie★ 56
- review-codeavibebuilder/claude-primeReview code for quality, correctness, and fit. Use when the user wants judgment on code that already exists — their own changes, a teammate's patch, a PR, branch, commit, diff, staged changes, or one or more files to look over. Activate on requests like review, look over, sanity check, critique, code review, or 'is this good?' The key signal is that the user wants evaluation of existing code and its tradeoffs, not implementation, debugging, or explanation. This skill works independently, but when plans, specs, task artifacts, or prior discussion exist, use them to understand why the code exists before judging it.Inginerie★ 120
- onboardhashgraph-online/awesome-codex-pluginsUse when taking over an existing codebase that has no living document. Produces a factual record of what already exists.Altele★ 1.4K
- private-house-codeSee-Sol-Lab/private-house-code-v2.5Keep coding work complete, readable, and proportionate to the task. Use when planning, implementing, debugging, testing, reviewing, or maintaining code, including bounded changes in larger repositories. Avoid unnecessary design and verification overhead. Does not apply to non-code conversation or writing.Inginerie★ 95
- refactorsandbaseai/sandbase-skillsPlan, implement, or review refactor work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests refactor work.Inginerie★ 203
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te