cc-best-practices
Improve Claude Code Workflows
Unclear prompts and crowded sessions reduce coding quality. This skill provides practical workflows for planning, verification, context control, automation, and independent review.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
Review the Skillstore skill "cc-best-practices" from https://skillstore.io/skills/dboeckli-cc-best-practices.md and its manifest at https://skillstore.io/api/skills/dboeckli-cc-best-practices/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„cc-best-practices“ wird verwendet. Help me ask Claude to fix an intermittent login failure.
Erwartetes Ergebnis:
Investigate login failures after session timeout. Inspect authentication refresh logic, add a reproducing test, implement the fix, and report test evidence.
„cc-best-practices“ wird verwendet. My session is long, and Claude repeats the same mistake.
Erwartetes Ergebnis:
- Record the missing constraint and any useful evidence.
- Clear the unrelated conversation context.
- Start again with the constraint, affected files, expected behavior, and a verification command.
„cc-best-practices“ wird verwendet. How should my team review a large refactor?
Erwartetes Ergebnis:
Use one session to implement the approved plan and another fresh session to inspect the diff, edge cases, and verification results.
Sicherheitsaudit
Mittleres RisikoAll 43 static alerts are false positives: the script uses fixed local validation commands, while the documentation alerts identify Markdown or benign examples. Two contextual risks remain because examples recommend sending logs to Claude and enabling broad unattended execution without adequate cautions.
Bestätigte Sicherheitsbedenken (2)
Risikofaktoren
⚙️ Externe Befehle (38)
📁 Dateisystemzugriff (2)
🌐 Netzwerkzugriff (1)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/dboeckli-cc-best-practices?utm_source=security_passport_badge)HTML-Badge
<a href="https://skillstore.io/skills/dboeckli-cc-best-practices?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dboeckli-cc-best-practices/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Einbettungskarte
<iframe src="https://skillstore.io/embed/skills/dboeckli-cc-best-practices.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
dboeckli. (2026). cc-best-practices security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1BibTeX-Zitat
@techreport{dboeckli-dboeckli-cc-best-practices-2026,
author = {dboeckli},
title = {cc-best-practices security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cc-best-practices security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "dboeckli"
date-released: "2026-09-26"
url: "https://skillstore.io/skills/dboeckli-cc-best-practices/audits/1"
identifiers:
- type: other
value: "skillstore:dboeckli-cc-best-practices:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Plan a Complex Change
Structure exploration, planning, implementation, and verification before editing several related files.
Standardize Team Instructions
Create a concise CLAUDE.md that records project-specific commands, architecture, testing rules, and repository conventions.
Scale Repetitive Analysis
Choose subagents, non-interactive commands, or parallel worktrees while preserving focused review and verification.
Diese Prompts ausprobieren
Rewrite my request with explicit scope, relevant files, constraints, expected behavior, and one runnable verification step.
Explore the affected code without editing. Then produce a sequenced plan with dependencies, risks, files, and verification commands.
Identify missing context behind repeated failures. Draft a fresh prompt that states the constraint, example, scope, and acceptance test.
Design separate writer and reviewer sessions using worktrees. Define ownership, allowed tools, handoff evidence, and final integration checks.
Bewährte Praktiken
- Provide a runnable check and request evidence from its output.
- Separate exploration, planning, implementation, and independent review for complex work.
- Keep persistent instructions short, project-specific, and necessary.
Vermeiden
- Do not combine unrelated tasks in one crowded session.
- Do not continue correcting the same failure without improving the original context.
- Do not grant broad automation permissions without reviewing data exposure and persistent changes.
Häufig gestellte Fragen
Does this skill modify my repository?
When should I use plan mode?
How should I verify generated code?
What belongs in CLAUDE.md?
Can Codex users apply this guidance?
Are the automation examples safe to run unchanged?
Entwicklerdetails
Autor
dboeckliLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
1cda4003aa9ea65a9606af00b33e9c706ef03e62
Aktualität der Wartung
30.9.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur