Skip to content
Back to skills

Coding Workflow

ASecurity

Best practices for coding, debugging, and refactoring. Use when reviewing code, debugging issues, refactoring, or establishing coding patterns.

  • 666 stars
  • 0 votes
  • 1 copy
  • 4 views
  • Added February 8, 2026
developmentdebuggingrefactoringsecurity

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill coding-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Coding Workflow?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coding Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-coding-workflow/badge)](https://www.skillsdirectory.com/skills/majiayu000-coding-workflow)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: coding-workflow
description: Best practices for coding, debugging, and refactoring. Use when reviewing code, debugging issues, refactoring, or establishing coding patterns.
---

# Coding Workflow Best Practices

## Code Review Approach

1. **Understand before changing**: Read the code thoroughly before suggesting modifications
2. **Check for patterns**: Look for existing patterns in the codebase and follow them
3. **Consider edge cases**: Think about null, empty, boundary conditions
4. **Security awareness**: Watch for injection, XSS, improper auth patterns

## Debugging Strategy

1. **Reproduce first**: Confirm the issue before attempting fixes
2. **Isolate the problem**: Narrow down to the smallest reproducible case
3. **Read error messages carefully**: They often contain the solution
4. **Check recent changes**: What changed since it last worked?
5. **Verify assumptions**: Test each assumption individually

## Refactoring Guidelines

1. **Tests first**: Ensure tests exist before refactoring
2. **Small steps**: Make incremental changes, verify each step
3. **One thing at a time**: Don't mix refactoring with feature changes
4. **Preserve behavior**: Refactoring should not change functionality

## Common Pitfalls

- Fixing symptoms instead of root causes
- Over-engineering simple solutions
- Ignoring existing patterns in the codebase
- Making changes without understanding context
- Skipping validation of user inputs at boundaries

## Accumulated Learnings

See [learnings.md](learnings.md) for session-learned insights that supplement these guidelines.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.