Global conventions
Skill bg-szy/TOP-SKILLS/skills/marketplace/global-conventions
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能,提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill global-conventionsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Follow consistent project structure, version control practices, environment configuration, code review processes, and development conventions across the entire application. Use this skill when organizing project files and directories, when writing commit messages or creating pull requests, when managing environment variables and configuration, when participating in code reviews, when defining testing requirements, when using feature flags, when maintaining changelogs, when documenting setup instructions, or when establishing consistent development practices across the team.
SKILL.md
1.7 KB, 198 tokens by cl100k_base, as published. Nobody here has run it
Global Conventions
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global conventions.
When to use this skill
- When organizing or restructuring project files and directories
- When writing commit messages, creating branches, or making pull requests
- When managing environment variables and configuration files
- When documenting features in README files or architecture documentation
- When participating in code reviews as reviewer or author
- When defining or following testing requirements before merging
- When implementing feature flags for incomplete or experimental features
- When maintaining changelog or release notes
- When managing project dependencies and documenting why they're used
- When setting up or updating contribution guidelines
- When ensuring consistent practices across the development team
- When making decisions about long-lived branches vs. feature flags
Instructions
For details, refer to the information provided in this file: global conventions
What ships with it: 1 file
10.6 KB alongside SKILL.md
- skill-report.json10.6 KB