qmu Co., Inc. avatar

qmu Co., Inc.

Official

@qmu · Japan, Tokyo

0Followers
|
7Public Repos
|
24Published Skills

Standardizes software delivery through structured ticket management, Git branch governance, and automated documentation generation for enterprise engineering teams.

Skills Distribution
DomainDeveloper To...Version Control Go.. (40%)Technical Document.. (30%)Release Management (30%)

Agent Skills by qmu Co., Inc.

Showing 24 vetted skills indexed across 1 GitHub repositories.

qmuqmu
1

discover-history

Search archived tickets under .workaholic/tickets/archive and sort matches by relevance.

Official
Basic
qmuqmu
1

commit

Automate safe git commits with pre-flight checks and structured messages.

Official
Basic
qmuqmu
1

write-changelog

Generate changelog entries from archived tickets and update CHANGELOG.md.

Official
Intermediate
qmuqmu
1

gather-ticket-metadata

Collect ticket metadata into a JSON payload via a single shell call.

Official
Basic
qmuqmu
1

drive-approval

Automates user approval, revision, and abandonment workflows for drive ticket implementations.

Official
Intermediate
qmuqmu
1

discover-source

Guide phased codebase exploration and generate structured discovery artifacts.

Official
Basic
qmuqmu
1

format-commit-message

Enforce structured Git commit messages with title, motivation, UX, and architecture sections.

Official
Basic
qmuqmu
1

write-story

Generate structured PR narratives from parallel agent outputs and commit references.

Official
Basic
qmuqmu
1

archive-ticket

Archive completed tickets, delegate commit creation, and update frontmatter.

Official
Basic
qmuqmu
1

translate

Translate English Markdown files while preserving formatting and frontmatter semantics.

Official
Basic
qmuqmu
1

drive-workflow

Read ticket content, apply patches, and implement changes with verification.

Official
Intermediate
qmuqmu
1

manage-branch

Check Git branch state and create timestamped topic branches.

Official
Basic
qmuqmu
1

write-terms

Generate a consistent term registry with frontmatter and change tracking.

Official
Basic
qmuqmu
1

assess-release-readiness

Analyze a code branch for release readiness and return a JSON verdict.

Official
Basic
qmuqmu
1

write-final-report

Append a standardized Final Report section to approved software tickets.

Official
Basic
qmuqmu
1

create-ticket

Generate standardized implementation tickets with frontmatter templates for .workaholic/tickets.

Official
Basic
qmuqmu
1

analyze-performance

Evaluate git branch decision-making and output a JSON summary with metrics.

Official
Intermediate
qmuqmu
1

gather-git-context

Collect Git branch, repository URL, tickets, and log into structured JSON.

Official
Basic
qmuqmu
1

discover-ticket

Analyze ticket overlaps to decide whether to create, merge, or split.

Official
Basic
qmuqmu
1

update-ticket-frontmatter

Update YAML frontmatter fields in ticket markdown files after implementation.

Official
Basic
qmuqmu
1

write-spec

Enforce frontmatter and content structure for spec documentation updates.

Official
Basic
qmuqmu
1

write-release-note

Generate structured release notes from branch story frontmatter to Markdown.

Official
Basic
qmuqmu
1

create-pr

Create or update GitHub pull requests from internal story files.

Official
Advanced
qmuqmu
1

write-overview

Generates a narrative branch overview from commit history into JSON.

Official
Basic

Frequently Asked Questions About qmu Co., Inc.

FAQPage Schema
What specific tasks can qmu perform regarding ticket management?

qmu enables the creation, archiving, and metadata extraction of implementation tickets stored in local directories. It supports updating YAML frontmatter, generating standardized final reports, and analyzing ticket overlaps to determine whether to merge, split, or create new implementation tasks.

Which engineering personas benefit from these capabilities?

Release engineers, technical leads, and documentation maintainers benefit from these capabilities. The system is designed for teams requiring strict adherence to commit message standards, structured pull request narratives, and consistent documentation practices across complex software repositories.

What are the prerequisites for running these operations?

Operations require a local repository environment with a structured .workaholic/tickets directory for storage. Users must ensure Git is configured for the target repository, as the system relies on branch state analysis, commit history parsing, and YAML frontmatter integrity within Markdown files.