Create TOML issue files with computed IDs and stage them with git.
npx skills add https://github.com/glhewett/public-skills --skill issues-create
Please help me install this Agent Skill. Skill: issues-create Source: https://github.com/glhewett/public-skills/tree/main/issues-create Command: npx skills add https://github.com/glhewett/public-skills --skill issues-create
Creating and tracking lightweight issues in a git-native workflow can be error-prone and inconsistent when done manually; this Skill automates generating properly formatted issue files so teams maintain consistent metadata and history in the repository.
Create a new issue titled Fix login bug with high priority assigned to alice by invoking the skill with flags --title Fix login bug --priority high --assigned-to alice.
High-intent search queries and answers about installing and using this skill.
To create git-native issues, this skill writes a new .issues/{id}.toml file with metadata like title, priority, assigned_to, and status, then stages the file with git add. It computes the next zero-padded 4-digit ID automatically from existing files.
Yes, you can set priority and assignment when creating issues by passing CLI-style flags like --priority and --assigned-to. If omitted, the skill falls back to sensible defaults when writing the TOML record.
Automating issue management without a dedicated tracker is handled by storing issues as lightweight TOML files in a git repository. This approach maintains consistent metadata, timestamps, and history directly in version control.
Yes, this method works with existing git repositories by operating within directories that store issues as .issues/{id}.toml files. It stages new issue files using git add so they are tracked and ready for commit.
The TOML issue file includes id, title, priority, assigned_to, status, closed, and created_at fields, along with a comments section placeholder. These fields ensure consistent issue tracking metadata across the repository.
Issue IDs are generated by computing the next zero-padded 4-digit number from existing issue files in the .issues directory. This ensures sequential, consistent identification for every new issue created.
glhewettRemove closed .toml issue files and commit the purge.
glhewettClose TOML issues by updating metadata, appending comments, and committing.
glhewettAssign a TOML issue file to the current git user and stage it.
glhewettUpdate issue status, commit changes, and create a feature branch.
