Files
awesome-copilot/skills/acquire-codebase-knowledge/assets/templates/CONVENTIONS.md
Satya K b8f3822748 Adds a new Agent Skill - Acquire-Codebase-Knowledge (#1373)
* feat(skill): add acquire-codebase-knowledge skill documentation

* feat(templates): add architecture, concerns, conventions, integrations, stack, structure, and testing documentation templates

* feat(references): add inquiry checkpoints and stack detection documentation

* feat(scan): add script to collect project discovery information for acquire-codebase-knowledge skill

* feat(skills): add acquire-codebase-knowledge skill for codebase mapping and documentation

* feat(scan): enhance scan script with absolute path handling and improved output variable validation

* feat(scan): replace bash script with Python script for project discovery information collection

* feat(skills): update acquire-codebase-knowledge skill to replace scan.sh with scan.py
2026-04-14 10:29:57 +10:00

1.3 KiB

Coding Conventions

Core Sections (Required)

1) Naming Rules

Item Rule Example Evidence
Files [RULE] [EXAMPLE] [FILE]
Functions/methods [RULE] [EXAMPLE] [FILE]
Types/interfaces [RULE] [EXAMPLE] [FILE]
Constants/env vars [RULE] [EXAMPLE] [FILE]

2) Formatting and Linting

  • Formatter: [TOOL + CONFIG FILE]
  • Linter: [TOOL + CONFIG FILE]
  • Most relevant enforced rules: [RULE_1], [RULE_2], [RULE_3]
  • Run commands: [COMMANDS]

3) Import and Module Conventions

  • Import grouping/order: [RULE]
  • Alias vs relative import policy: [RULE]
  • Public exports/barrel policy: [RULE]

4) Error and Logging Conventions

  • Error strategy by layer: [SHORT SUMMARY]
  • Logging style and required context fields: [SUMMARY]
  • Sensitive-data redaction rules: [SUMMARY]

5) Testing Conventions

  • Test file naming/location rule: [RULE]
  • Mocking strategy norm: [RULE]
  • Coverage expectation: [RULE or TODO]

6) Evidence

  • [path/to/lint-config]
  • [path/to/format-config]
  • [path/to/representative-source-file]

Extended Sections (Optional)

Add only for large or inconsistent codebases:

  • Layer-specific error handling matrix
  • Language-specific strictness options
  • Repo-specific commit/branching conventions
  • Known convention violations to clean up