skills.rest
BrennonTWilliams
BrennonTWilliamsCOMMUNITY
Explore all skills by this author →
GitHub

ll-normalize-issues

Validate issue filename ID prefixes and rename duplicates across project directories.

7|2|Updated Jan 3, 2026
Search Tags:#automation#file management#issue tracking#repository maintenance#naming convention
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-normalize-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ll-normalize-issues
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/ll-normalize-issues
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill ll-normalize-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves inconsistencies in project issue tracking by identifying and correcting filenames that lack proper IDs or contain duplicate identifiers across different issue types.

Core Features & Use Cases

  • ID Validation: Automatically scans project files to ensure every issue follows a consistent naming convention (e.g., BUG-007, FEAT-007).
  • Conflict Resolution: Detects duplicate IDs and missing tags that disrupt automated project management workflows.
  • Use Case: Use this tool when your repository has accumulated messy issue filenames, ensuring your project management dashboard correctly maps every file to its corresponding task.

Quick Start

Run the ll-normalize-issues skill to scan the current directory and automatically rename files to match the required project ID format.

Frequently Asked Questions about ll-normalize-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize issue filenames with missing IDs in my repository?▼

To standardize issue filenames, this skill scans your repository directories to identify files lacking proper ID prefixes and automatically renames them to match the required project naming convention.

What is the best way to detect and resolve duplicate issue tracking IDs?▼

The best way to resolve duplicate issue tracking IDs is to run a validation scan, which detects conflicting identifiers across different issue types and project files for batch correction.

How does issue filename validation work for bug and feature tracking?▼

Issue filename validation works by checking repository file structures against standardized naming conventions, ensuring every bug and feature file has a unique, correctly formatted ID prefix.

Do I need filesystem access to batch rename issue files?▼

Yes, you need direct filesystem access to perform batch renaming and validate issue metadata, as the tool operates directly on your project's directory structures to correct inconsistencies.

Can I fix inconsistent issue filenames across multiple project directories?▼

Yes, you can fix inconsistent issue filenames across multiple project directories, as the tool scans the file structure to ensure compliance with standardized naming conventions for all tracked issues.

Related Skills

Explore More Software Engineering Skills→
LightconeResearchLightconeResearch
18

lc-from-code

Scan source files to generate or augment astra.yaml and universes/baseline.yaml.

Official
Advanced
catlog22catlog22
511

manage-issue

Create, list, update, close, and link issues in a JSONL store.

Community
Intermediate
antgroupantgroup
16

file-manager

Automate file categorization, batch renaming, duplicate detection, and directory synchronization.

Official
Intermediate
kinncjkinncj
23

gherkin-authoring

Generate and update Gherkin story files with EPIC-NNNN IDs and standard tags.

Community
Intermediate