skill upstream pr

Engineering Community

Skill notes

Repo Sync Before Edits (mandatory)

Before any modification to the cloned fork, pull the latest from the fork's tracked branch: If the working tree is dirty: stash, sync, pop. If origin is missing or conflicts occur: stop and ask the user. A stale fork that PRs yesterday's tree is worse than no PR.

When to Use

User shares a GitHub URL to a public skill repo and asks to "improve", "level up", or "contribute to" it User says "open a PR to this skill" or "suggest improvements upstream" The target skill scores below 85/8 on asm eval and the user wants the upstream author to benefit Do not trigger for: editing a local skill with no upstream, authoring a brand-new skill, publishing to the ASM registry, or bulk-improving many repos in one pass. One skill → one PR.

Prerequisites

Verify each before cloning anything. Stop and tell the user if any fails. asm on PATH (command -v asm) gh on PATH and authenticated (gh auth status) git on PATH Network access to GitHub

Input

The user provides a GitHub reference to a skill. Accept any of: https://github.com/owner/repo https://github.com/owner/repo/tree/<branch>/<path/to/skill> github:owner/repo[#ref][:path] Normalize to owner, repo, optional ref, optional path. If path is not given and the repo has multiple SKILL.md files, ask the user which one.

Workflow

Execute phases in order. Do not skip or reorder.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@luongnv89 · MIT
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-upstream-pr.preview
# Expected output

- A new branch on the user's fork of `$OWNER/$REPO`
- A public PR on `$OWNER/$REPO` with a before/after metrics table and friendly tone
- A local `.asm-improver/` directory with baseline, iterations, report, and `pr-body.md`

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.