update-content

Update Content Skill

Generic file update Skill that respects RULE.md constraints and maintains format consistency.

When to use this Skill

• User says "update", "edit", "modify", "change"
• User references existing file or content
• User requests content revision
• User mentions specific file to update

Workflow

1. Identify Target File

If user provides file path:

• Verify file exists
• Confirm with user if ambiguous

If user provides topic/title only:

• Search for file using Grep or Glob
• Pattern: **/*keyword*.md
• If multiple matches: present list, ask user to choose
• If no matches: report not found, offer to create instead

Search strategies:

1. Filename match: find . -name "*keyword*"
2. Content match: grep -r "keyword" .
3. README.md index: Search README.md files for references

2. Read Current Content

Load existing file:

• Use Read tool to load full content
• Understand current structure:
  • Frontmatter (if present)
  • Section headings
  • Content organization
  • Formatting style

Analyze format:

• Identify markdown structure
• Note any special formatting
• Detect metadata or frontmatter
• Understand content layout

3. Read Directory RULE.md

Locate and read RULE.md:

1. Check file's directory for RULE.md
2. If not found, check parent directories (inheritance)
3. Parse RULE.md for update rules

Check for:

• Are updates allowed? (some directories may be append-only or immutable)
• Format requirements to maintain
• Required fields that must be preserved
• Update workflow (e.g., "always add changelog entry")
• Versioning requirements

Example RULE.md update rules:

## Update Rules
- Preserve frontmatter fields: title, date, tags
- Add "Last updated" timestamp to frontmatter
- Append changes to "Changelog" section
- Maintain markdown heading structure

4. Execute Update

Apply requested changes:

• Use Edit tool for targeted changes
• Or Write tool for complete rewrites (if needed)
• Maintain existing format per RULE.md
• Preserve required fields/structure