edward321416-maker
Community@edward321416-maker
Registry of GitHub-centric repository skills covering issue-to-PR task execution, evidence-backed planning, edit-collision detection, and skill frontmatter validation fixtures.
Agent Skills by edward321416-maker
Showing 6 vetted skills indexed across 1 GitHub repositories.
edward321416-makerush-github-task-flow
Carry a bounded task from GitHub issue through branch, validation, and pull request.
edward321416-makerush-game-meeting-plan
Converts game development meeting notes and chat transcripts into read-only implementation plans.
edward321416-makerush-work-announcement
Draft repository-evidence-based development announcements and publish approved text to message channels.
edward321416-makerush-concurrent-edit-coordination
Classifies overlap between two actively-editing workstreams using real git diff evidence.
edward321416-makerush-repo-evidence-plan
Inspects a repository and produces a bounded, evidence-backed implementation plan without modifying files.
edward321416-makerush-discord-repo-cross-reference
Cross-references Discord discussion claims against repository code, tests, and documentation evidence.
Frequently Asked Questions About edward321416-maker
FAQPage SchemaWhat tasks can I accomplish with edward321416-maker's skills?▼
You can execute a GitHub issue end-to-end into an open validated PR, generate evidence-backed implementation plans from repository inspection, convert game-development meeting notes into scoped plans, draft repository-history-based work announcements, detect concurrent edit collisions, and cross-reference Discord claims against repo evidence.
Who are these skills designed for?▼
Software engineers and game-development teams working in GitHub repositories who need disciplined issue-to-PR execution, collision checks between parallel workstreams, and auditable communication grounded in actual commit history rather than speculation.
How do the GitHub task-flow skills behave at runtime?▼
The task-flow skill treats GitHub as the source of truth: it creates an isolated branch, validates changes, and opens a pull request. It never merges unless merging is separately and explicitly requested, keeping the default outcome a safe, reviewable PR.
Why does the manifest contain so many fixture skills?▼
Most entries are validator test fixtures exercising the Agent Skills spec: invalid SemVer, out-of-range risk tiers, nested metadata, malformed YAML, oversized names, and bad allowed-tools formats. They exist to verify frontmatter validation, not to provide end-user functionality.
What are the prerequisites and risk levels of these skills?▼
Skills declare scope (global or domain), SemVer versions, and L0-L3 risk tiers; one fixture notes compatibility requiring git and internet access. Most operational skills are low-risk L0 read-only or planning actions, while the GitHub task-flow skill is L3 because it modifies branches and opens PRs.