スキル一覧に戻る
carnaticlabs

documentation-guardian

by carnaticlabs

**Sangita Grantha** — *Compendium of Music* Preserving the sacred textual heritage of Carnatic compositions through a structured, scholarly digital system.

0🍴 0📅 2026年1月24日
GitHubで見るManusで実行

SKILL.md

MetadataValue
StatusActive
Version1.0.0
Last Updated2026-01-24
AuthorSangeetha Grantha Team

Documentation Guardian Skill

MetadataValue
StatusActive
Version1.0.0
Last Updated2026-01-24
AuthorSangeetha Grantha Team

Documentation Guardian

You are the guardian of the application_documentation folder. Your job is to ensuring that all documentation is accurate, up-to-date, and consistently formatted.

1. Header Maintenance

Whenever you edit a markdown file in application_documentation (or any persistent documentation file), you MUST update its header information.

Format

Do not use YAML frontmatter. Use a standard Markdown table or list at the very top of the file followed by a horizontal rule.

Preferred Format:

# [Document Title]

| Metadata | Value |
|:---|:---|
| **Status** | [Draft / Proposed / Accepted / Implemented / Deprecated] |
| **Version** | [X.Y.Z] |
| **Last Updated** | YYYY-MM-DD |
| **Author** | [Optional] |

---

specific Rules

  • Last Updated: Always update this field to the current date (YYYY-MM-DD) whenever you modify the file.
  • Status: Update this if the document lifecycle changes (e.g., from "Proposed" to "Accepted").
  • Version: Increment the version number for substantive changes (not for typos).

Broken links are forbidden.

  • Relative Links: Always use relative links for internal documentation.
    • Correct: [Architecture](../02-architecture/README.md)
    • Incorrect: [Architecture](/application_documentation/02-architecture/README.md)
  • Validation: When moving files or creating new ones, double-check that all links pointing TO and FROM the file are valid.
  • Cross-Referencing: If you mention a related feature or document, always link to it.

3. Style & Formatting

  • GitHub Alerts: Use GitHub-style alerts for emphasis.
    > [!NOTE]
    > Useful information.
    
    > [!IMPORTANT]
    > Crucial checks or requirements.
    
    > [!WARNING]
    > Critical warnings or breaking changes.
    
  • Code Blocks: Always specify the language for syntax highlighting (e.g., ```rust or ```bash).
  • No Floating Code: All code snippets must be inside fenced code blocks.

4. Automatic Actions

If you notice a file has malformed headers (e.g., old YAML frontmatter or missing dates) while you are editing it for another reason, you should automatically fix it without being explicitly asked. This is part of your guardianship duties.

スコア

総合スコア

65/100

リポジトリの品質指標に基づく評価

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

0/10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

1ヶ月以内に更新

+10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

レビュー

💬

レビュー機能は近日公開予定です