Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Quality] Establish Standard Linter Configuration for Agent PR Approvals #1428

New Issue
Closed
opened 2026-03-24 13:04:46 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 13:04:46 +00:00
Owner
Copy Link

Context: Agents sometimes bypass tox -e lint internally without a strict upstream rejection.

Acceptance Criteria:

  • Enforce ruff or flake8 heavily inside Gitea branch protection workflows.
  • Deny squash merges if lint warnings exceed thresholds.
**Context:** Agents sometimes bypass `tox -e lint` internally without a strict upstream rejection. **Acceptance Criteria:** - Enforce `ruff` or `flake8` heavily inside Gitea branch protection workflows. - Deny squash merges if lint warnings exceed thresholds.
Timmy commented 2026-03-24 13:22:01 +00:00
Author
Owner
Copy Link

Implementation Instructions

Kimi, please establish standard linter configuration for agent PR approvals.

Step-by-step approach:

  1. Audit current linting setup:

    • Review tox.ini [lint] environment
    • Check .ruff.toml configuration
    • Review pre-commit hooks in .githooks/

  2. Standardize agent linting requirements:

    • All agent PRs must pass tox -e lint
    • Create .github/pull_request_template.md with linting checklist
    • Document linting standards in CONTRIBUTING.md

  3. Add stricter rules for agents:

    • Enable additional ruff rules for code quality
    • Configure max line length consistently
    • Enforce import sorting

Key files to modify:

  • .ruff.toml - add stricter agent-specific rules
  • tox.ini - ensure lint environment is comprehensive
  • CONTRIBUTING.md - document agent linting standards
  • .github/pull_request_template.md - add linting checklist

Acceptance criteria:

  • All current code passes new linting rules
  • Clear documentation of linting standards
  • Template for agent PRs includes linting verification
## Implementation Instructions Kimi, please establish standard linter configuration for agent PR approvals. **Step-by-step approach:** 1. **Audit current linting setup:** - Review `tox.ini` [lint] environment - Check `.ruff.toml` configuration - Review pre-commit hooks in `.githooks/` 2. **Standardize agent linting requirements:** - All agent PRs must pass `tox -e lint` - Create `.github/pull_request_template.md` with linting checklist - Document linting standards in `CONTRIBUTING.md` 3. **Add stricter rules for agents:** - Enable additional ruff rules for code quality - Configure max line length consistently - Enforce import sorting **Key files to modify:** - `.ruff.toml` - add stricter agent-specific rules - `tox.ini` - ensure lint environment is comprehensive - `CONTRIBUTING.md` - document agent linting standards - `.github/pull_request_template.md` - add linting checklist **Acceptance criteria:** - All current code passes new linting rules - Clear documentation of linting standards - Template for agent PRs includes linting verification
kimi was assigned by Timmy 2026-03-24 13:22:04 +00:00
kimi was unassigned by Timmy 2026-03-24 19:32:13 +00:00
Timmy closed this issue 2026-03-24 21:54:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1428
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?