Skip to content
Back to skills

925 Location Of Fix Documentationinstructions F75621f0

ASecurity

All bug fixes and issue resolution documentation should be placed in: ``` ..\docs\explanation\fixes\ ```

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
documentationtestingdocumentation

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 925-location_of_fix_documentationinstructions_f75621f0 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 925 Location Of Fix Documentationinstructions F75621f0?

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

Security grade badge for 925 Location Of Fix Documentationinstructions F75621f0
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-925-location-of-fix-documentationinstructions-f756/badge)](https://www.skillsdirectory.com/skills/tools-only-925-location-of-fix-documentationinstructions-f756)

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

SKILL.md
---
applyTo: '**'
---

# Fix Documentation Location

## Documentation Directory
All bug fixes and issue resolution documentation should be placed in:
```
..\docs\explanation\fixes\
```

## File Naming Convention
Use descriptive, uppercase names with underscores:
- `[ISSUE_NAME]_FIX.md` 
- Example: `TABULAR_DATA_CSV_STORAGE_FIX.md`
- Example: `CSV_COLUMN_CONSISTENCY_FIX.md`

## Required Documentation Structure
Each fix documentation file must include:

### 1. Header Information
- Fix title
- Issue description
- Root cause analysis
- Version implemented

### 2. Technical Details
- Files modified
- Code changes summary
- Testing approach
- Impact analysis

### 3. Validation
- Test results
- Before/after comparison
- User experience improvements

## Integration Process
When documenting a fix:
1. Create markdown file in `..\docs\fixes\`
2. Include current config.py version
3. Reference related functional tests
4. Update any relevant feature documentation if the fix affects existing features

## Cross-References
Fix documentation may reference:
- Related feature documentation in `..\docs\features\`
- Functional test files in `functional_tests\`
- Configuration changes in `config.py`

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.