# Project Maintainer

> A skill to automate the maintenance of project documentation files like STATUS.md, HISTORY.md, and PROJECT_TODO.md.

- Skill: `reutfarkash/project-maintainer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add reutfarkash/project-maintainer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/reutfarkash/project-maintainer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: ReutFarkash (https://skillmd.com/u/reutfarkash)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/reutfarkash/project-maintainer

---


# Project Maintainer

## Overview

This skill provides a set of commands to automate the process of updating and maintaining the project's documentation files. It ensures that the `STATUS.md`, `HISTORY.md`, and `PROJECT_TODO.md` files are tethered to the actual Git state of the skill submodules.

## Commands

### `/review_project`

Reviews all project documentation, updates where necessary, and generates a status report manifest.

**Workflow:**

1.  **Git Status Guard:** For each submodule (`skills/public`, `skills/internal`), check for uncommitted changes using `git status --porcelain`.
    *   If changes are present, **stop and ask the user** if they wish to commit them before proceeding.
    *   If they agree, perform `git add .` and `git commit -m "<user_provided_message>"` within that submodule.
2.  **Identify Submodule States:** Once clean, get the current short Git SHA (`git rev-parse --short HEAD`) for both submodules.
3.  **Find Files:** Locate all `STATUS.md`, `HISTORY.md` files within the `meta/skills/` directory and the `PROJECT_TODO.md` in the root.
4.  **Update Status Files:** For each `STATUS.md` file, update the `Last Update` date and the `Last Verified SHA`.
5.  **Cheat Sheet Sync (Periodic):** 
    *   Once in a while (e.g., if it's the first review of the month, or if the user explicitly asks to "Review the full workflow"), read the `GEMINI_WORKFLOW_CHEATSHEET.md` in the project root.
    *   Verify that the submodule paths, GitHub URLs, and launch commands still match the actual project structure.
    *   Suggest updates if any discrepancies are found.
6.  **Update `PROJECT_STATUS.md`:** Create or update a `PROJECT_STATUS.md` file in the project root with a manifest report.

**Example Usage:**

"Review the project status." or "Perform a full project and workflow review."

### `/log_change <skill_name> "<message>"`

Appends a new entry to the `HISTORY.md` file, tethered to the current Git SHA.

**Workflow:**

1.  **Git Status Guard:** Identify which submodule the skill belongs to. Check for uncommitted changes (`git status --porcelain`).
    *   **Stop and ask the user** to commit if the submodule is dirty.
2.  **Identify Submodule SHA:** Once the submodule is clean, run `git rev-parse --short HEAD`.
    *   If skill is `quartz-blog-post`, use SHA from `skills/internal`.
    *   Otherwise, use SHA from `skills/public`.
3.  **Identify Target File:** Locate the `HISTORY.md` file at `meta/skills/<skill_name>/HISTORY.md`.
4.  **Construct New Entry:** Create a formatted entry: `### YYYY-MM-DD [ref: <sha>]`.
5.  **Append and Write:** Prepend the new entry and message to the existing content.

**Example Usage:**

`/log_change obsidian-chat-summary "Refactored output path to /output folder."`

### `/update_status <skill_name> --status "<new_status>"`

Updates the `Status` and `Last Verified SHA` in a skill's `STATUS.md` file.

**Workflow:**

1.  **Git Status Guard:** Check the appropriate submodule for uncommitted changes. Ask the user to commit if dirty.
2.  **Identify Submodule SHA:** Get the current short SHA from the appropriate submodule.
3.  **Identify Target File:** Locate the `STATUS.md` file at `meta/skills/<skill_name>/STATUS.md`.
4.  **Update Content:** Replace `Status: <old>` and `Last Verified SHA: <old>` with the new values.

**Example Usage:**

`/update_status conversation-flow --status "Active"`

### `/increment_version <skill_name> --type [patch|minor|major]`

Increments the skill version in its own `SKILL.md` frontmatter.

**Workflow:**

1.  **Locate Skill:** Find the `SKILL.md` for the specified `<skill_name>`.
2.  **Read Frontmatter:** Parse the YAML to get the current `version`.
3.  **Calculate New Version:** Increment the version string (e.g., `v1.0.0` -> `v1.0.1` for patch).
4.  **Update SKILL.md:** Replace the `version:` line with the new version.
5.  **Log History:** Append the version change to the skill's `HISTORY.md` file in the `meta/` directory.
6.  **Trigger Git Tag:** If `git-flow-automator` is active, request it to tag the repository containing the skill with the new version.

**Example Usage:**

`/increment_version git-flow-automator --type patch`

### `/add_todo "<task>"`

Adds a new task to the `PROJECT_TODO.md` file.

**Workflow:**

1.  **Identify Target File:** Locate the `PROJECT_TODO.md` file in the project root.
2.  **Append and Write:** Insert the new task `- [ ] <task>` under the `## 🎯 Open Tasks` section.