git-and-docs

Git and Docs

This skill coordinates git commit creation and documentation generation.

When to Use

• During /end when user requests commits
• During /end when user requests documentation
• When explicitly asked to commit session work
• When explicitly asked to generate documentation

Input

• sessionPath: Path to the current session directory
• request:
  • commit: boolean - Whether to create commits
  • docs: boolean - Whether to generate documentation
• commitOptions (optional):
  • message: Custom commit message (optional)
  • files: Specific files to commit (optional, default: all staged)
• docsOptions (optional):
  • outputPath: Where to save docs (default: session directory)
  • sections: Which sections to generate

Responsibilities

• Read plan.md and session.md via artifact-fs-manager
• If commits requested:
  • Call git-commit-manager agent
  • Pass plan and session context
  • Return commit result
• If docs requested:
  • Call docs-generator agent
  • Specify output path
  • Return generated docs path
• Return combined results

MUST NOT

• Change session Status (owned by session-manager and dev-session-closure)
• Execute development steps
• Modify plan or session content
• Make decisions about what to commit (user decides)

Process

Step 1: Load Context

1. Use artifact-fs-manager to read plan.md
2. Use artifact-fs-manager to read session.md
3. Extract relevant context for commit/docs

Step 2: Handle Commit Request

If commit: true:

1. Prepare context for git-commit-manager:

   • Task description from session
   • Completed steps from session
   • Files modified (from step completion tickets)

2. Call git-commit-manager agent with:

   • Session context (plan.md + session.md paths)
   • Custom message if provided
   • File list if provided

3. Receive commit result:

   • Commit hash
   • Commit message
   • Files committed

Step 3: Handle Docs Request

If docs: true:

1. Determine output path: