gemini-cli-extensions / gemini-cli-extensions/conductor

[Feature Request] Add Mandatory Pre-commit Cleanup and Screenshot Storage Rules to Standard Workflow

Open
#29 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
Python
Stars
3.7k
Forks
295
Avg merge
9m
Merged PRs (30d)
1

Description

Problem Description

During the execution of tracks using AI agents (e.g., via /conductor:implement), agents frequently generate temporary artifacts for verification and debugging, such as:

  • Build logs (debug.log,build.log, npm-debug.log).
  • UI verification screenshots (*.png, *.jpg, *.webp) via chrome-devtools-mcp.

Without explicit rules, AI agents tend to use git add . or git add -u, leading to these temporary files being accidentally committed into the repository history. This causes repository bloat and potential disclosure of local environment information (like absolute file paths in logs).

Proposed Solution

1. Update workflow.md Template

Add a mandatory "Pre-commit Cleanup & Verification" step in both Standard Task Workflow and Phase Completion Protocol.

Requirement:
AI agents MUST physically delete all temporary logs and screenshots and execute git status to verify a clean working area before performing any git commit.

2. Strengthen Default .gitignore

The framework should recommend or include common debug patterns in its base .gitignore:

*.log
*.png
*.jpg
*.jpeg
*.webp
3. Standardize Screenshot Storage for AI

Add a rule to the system instructions or .gemini/GEMINI.md template:

"Unless explicitly requested otherwise by the user, all screenshots generated via take_screenshot MUST be stored in the system's temporary directory, never in the project root."

Expected Benefit

  • Maintains a clean and professional repository history.
  • Prevents accidental disclosure of environment-specific metadata.
  • Reduces the manual effort for human developers to "clean up" after the AI agent.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the workflow.md template, the base .gitignore, and the .gemini/GEMINI.md template mentioned in the issue. Update the Standard Task Workflow and Phase Completion Protocol with cleanup and git status verification, add the requested ignore patterns and screenshot-storage rule, and verify that all three requirements are represented.

Written by the indexing model from the issue text.

Assessment

Tech stack
git
Domain
documentation, tooling
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.