tidy

Commit, push, and update issues at end-of-workflow.

11|2|Updated Jan 3, 2022
One-click install
npx skills add https://github.com/hay-kot/dotfiles --skill tidy-hay-kot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tidy
Source: https://github.com/hay-kot/dotfiles/tree/main/.ai/skills/tidy
Command: npx skills add https://github.com/hay-kot/dotfiles --skill tidy-hay-kot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tidy implements a comprehensive end-of-workflow checklist to ensure changes are committed, pushed, and issues are updated, preventing lost work and status drift.

Core Features & Use Cases

  • Stepwise state assessment: identify uncommitted changes, stash items, and in-progress issues, with guidance to resolve.
  • Enforced push cycle and quality gates: ensure code is validated and synchronized remotely before marking work complete.
  • Issue hygiene and follow-ups: update or close completed issues and automatically create follow-ups when necessary.

Quick Start

Run the tidy command at the end of your work session to ensure all changes are committed, pushed, and issues updated.

Frequently Asked Questions about tidy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure git changes are committed, pushed, and issues updated before ending a work session?

To ensure git changes are committed, pushed, and issues updated, run an automated end-of-workflow cleanup command that performs state checks, applies quality gates, and validates a clean push and sync.

What is the best way to automate git workflow cleanup and issue tracking updates?

Automating git workflow cleanup and issue tracking updates involves a stepwise process that identifies uncommitted changes, enforces a push cycle, updates completed issues, and automatically creates necessary follow-ups.

How do quality gates work during a git push and issue close workflow?

Quality gates during a git push and issue close workflow validate code and ensure it is synchronized remotely before marking work complete, preventing lost work and status drift.

Can I automatically create follow-up issues when closing completed tasks in an issue tracker?

Yes, you can automatically create follow-up issues when closing completed tasks by running an end-of-workflow checklist that updates issue hygiene and generates new tracking items when necessary.

Does this git cleanup workflow handle uncommitted changes and stash items?

Yes, this git cleanup workflow handles uncommitted changes and stash items through a stepwise state assessment that identifies in-progress issues and provides guidance to resolve them before pushing.

Why do I need to run a state check before pushing code and closing issues?

Running a state check before pushing code and closing issues prevents lost work and status drift by ensuring all local changes are identified, committed, and synchronized with the remote repository.