learn-common-utils

Scan the common/ module and document utility classes into knowledge_common_utils.md.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill learn-common-utils
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn-common-utils
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/learn-common-utils
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill learn-common-utils

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill collects and documents common utility classes, shared services, and helper methods to prevent duplicate implementations and promote reuse across the codebase.

Core Features & Use Cases

  • Scan the repository to identify util/helper/constant/service units in the common module.
  • Document and catalog utilities to enable reuse, reduce redundancy, and improve maintainability.
  • Use as a knowledge source to guide future development and avoid duplicating existing implementations.

Quick Start

Scan the project to build a knowledge_common_utils.md in the base_knowledge/structures/propose/ directory.

Frequently Asked Questions about learn-common-utils

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

FAQPage Schema
How do I catalog common utils to prevent code duplication?

To document shared services and prevent duplicates, scan the codebase to identify utility classes and helper methods, then generate a structured knowledge base file detailing class names, methods, and usage patterns for reuse.

What is the best way to build a knowledge base of existing helper methods?

Building a knowledge base of helper methods involves scanning the common module to extract utility units and generating a structured markdown document detailing usage patterns to guide future development and reduce redundancy.

How do I document shared services for code reuse in a repository?

Document shared services for code reuse by applying a scan across the codebase to collect utility classes and constants, ensuring outputs follow a structured template suitable for integration into the knowledge pipeline.

Does this utility documentation approach work with a common module structure?

This utility documentation approach works primarily with a common module structure, scanning it to identify util, helper, constant, and service units to catalog for centralized reuse and maintainability.

Why should I scan the codebase to identify utility classes?

Scanning the codebase to identify utility classes prevents duplicate implementations by creating a centralized knowledge source that promotes reuse, reduces redundancy, and improves overall maintainability.