editing-code-rules
Prioritizes the method for editing code and defines verbosity levels.
Best use case
editing-code-rules is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Prioritizes the method for editing code and defines verbosity levels.
Teams using editing-code-rules should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/editing-code-rules/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How editing-code-rules Compares
| Feature / Agent | editing-code-rules | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Prioritizes the method for editing code and defines verbosity levels.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Editing Code Rules Skill
<identity>
You are a coding standards expert specializing in editing code rules.
You help developers write better code by applying established guidelines and best practices.
</identity>
<capabilities>
- Review code for guideline compliance
- Suggest improvements based on best practices
- Explain why certain patterns are preferred
- Help refactor code to meet standards
</capabilities>
<instructions>
When reviewing or writing code, apply these guidelines:
- Editing Code (prioritized choices):
- Return completely edited file
- Verbosity: I may use V=[0-3] to define code detail:
- V=0 code golf
- V=1 concise
- V=2 simple
- V=3 verbose, DRY with extracted functions
</instructions>
<examples>
Example usage:
```
User: "Review this code for editing code rules compliance"
Agent: [Analyzes code against guidelines and provides specific feedback]
```
</examples>
## Memory Protocol (MANDATORY)
**Before starting:**
```bash
cat .claude/context/memory/learnings.md
```
**After completing:** Record any new patterns or exceptions discovered.
> ASSUME INTERRUPTION: Your context may reset. If it's not in memory, it didn't happen.Related Skills
file-management-rules
Specifies file management guidelines, including including full file paths as comments, updating project structure in AI.MD, and maintaining package.json. This rule ensures organized and well-documente
eslint-rules
Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.
cursor-rules
This skill should be used when creating or editing Cursor rules files (.mdc format) in the .cursor/rules directory. Provides guidance on rule types, frontmatter configuration, effective rule writing patterns, and best practices for structuring AI instructions for Cursor IDE.
cursor-rules-writing
Create Cursor IDE rules in .mdc format with proper frontmatter, glob patterns, and cross-references. Covers rule structure, file organization, triggering mechanisms, and quality standards. Use when creating or modifying Cursor rules for context injection.
creating-cursor-rules-skill
Expert guidance for creating effective Cursor IDE rules with best practices, patterns, and examples
create-rules
Create or update Cursor Rules (.mdc files) and Skills (SKILL.md). Use when creating rules, adding coding standards, setting up conventions, updating .cursor/rules/, or converting rules to skills. Defines standard format, naming, frontmatter, token budget.
crafting-rules
Use when creating or modifying OpenCode rules (.md/.mdc files) that customize agent behavior. Helps extract patterns from conversation history, analyze project conventions (AGENTS.md, linters, package.json), and draft well-formatted rules with appropriate globs/keywords. Trigger when user wants to create a rule, codify repeated instructions, persist guidance across sessions, or customize agent behavior for specific files or topics.
containerization-rules
Rules for creating and maintaining Dockerfiles.
common-rules
Tüm skill'ler için ortak kurallar ve standartlar. Git workflow, code style, documentation ve performance best practices içerir.
checkstyle-rules
Use when applying Checkstyle built-in checks for Java code including naming conventions, code metrics, and suppressions.
assistant-behavior-rules
AI assistant behavior rules including response formatting and interaction patterns
ameba-custom-rules
Use when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.