Skip to content
Skills Library
Programming · Analysis

pullstack-update

/pullstack-update

Use when a project the user already pulled features from has a newer version, and they ask what changed since — "X shipped v2, anything worth taking?", "re-check X", "what's new in X since we ported", "update our port of X".

Repository
pullstack ↗
Licence
MIT
Last repository change
26.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when a project the user already pulled features from has a newer version, and they ask what changed since — "X shipped v2, anything worth taking?", "re-check X", "what's new in X since we ported", "update our port of X".

Triggers from the description

X shipped v2, anything worth taking?re-check Xwhatupdate our port of X
Original author description

Use when a project the user already pulled features from has a newer version, and they ask what changed since — "X shipped v2, anything worth taking?", "re-check X", "what's new in X since we ported", "update our port of X".

How it works

  1. Steps
  2. Common mistakes
Original SKILL.md headings · 27 lines, 308 words
SKILL.md preview
---
name: pullstack-update
description: Use when a project the user already pulled features from has a newer version, and they ask what changed since — "X shipped v2, anything worth taking?", "re-check X", "what's new in X since we ported", "update our port of X".
---

# Pullstack update

Report only what an upstream gained, changed or removed since the version this project last learned from.

`<pullstack>` below is the `pullstack` skill folder installed next to this one (`<this skill dir>/../pullstack`). This skill reuses its brief, sandbox and build steps.

## Steps

1. **Find the baseline.** The old report, `~/.cache/pullstack/reports/<name>.md`, records the old SHA or SHA-256 in its Snapshot. No report → ask the user for the old version (tag, commit, or the old artifact). Nothing known → run `pullstack` instead; there is no baseline to diff.
2. **Re-check the licence** of the new version. Projects relicense. New features follow the new licence's route; code already copied keeps the terms it was copied under.
3. **Fetch both versions** into `~/.cache/pullstack/work/<name>-old` and `<name>-new`, by the rules of `pullstack` step 2. Artifacts are unpacked through `<pullstack>/scripts/sandbox.sh`.
4. **Narrow before reading.**
   - Repo: in one clone, fetch both commits (`git fetch --depth 1 origin <sha>`, once per side), then `git diff --stat <old> <new>`.
   - Artifact: follow "Two builds of one app" in `<pullstack>/references/artifact-route.md`.
   - Changelogs and release notes are leads to check, never evidence.
5. **Dissect the changed areas only**, with the brief from `<pullstack>/SKILL.md`. Set Focus to `changes between <old> and <new>`, and add: "Matrix rows are only features added, changed or removed between the two versions. For each changed feature this project already ported, say whether the port needs the change." Delete both work folders once the report is written.
6. **Continue with `pullstack` steps 5 to 7**: the user picks, then plan and build.

## Common mistakes

| Mistake | Fix |
|---|---|
| Re-listing features that were already there | Rows cover the diff between the two versions only |
| Taking the changelog's word | Cite the changed code |
| Assuming the old licence still holds | Step 2 |

Versions

The database has no other skills named pullstack-update.

Database snapshot: 13.11.2026 · package version a6ac75017e2c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90pullstack-help
    Use when the user asks how pullstack works, which pullstack skills exist, or what it needs — "/pullstack-help", "pullstack help", "what can pullstack do".
  • 90pullstack
    Use when the user names another project — a repository URL or path, or with no repo, a desktop app, APK, web app or binary — and wants its features brought into the current project: "pullstack <X>", "take features from X", "compare my project with X and upgrade it", "what does X…
  • 100update-docs
    Update public documentation in docs/public/ when features or tools change. Triggers on "/update-docs", "update docs", "update documentation".
  • 90update
    Use when the user wants to update the frontend harness in this project to the plugin's current version.
  • 90update
    Update finolabs-vibecode with the user's permission and walk them through what the new version asks of them, show what is new without changing anything, target the latest or a chosen released version, pin or unpin a version, skip a release, or stop update notices. Use when the…
  • 90update-rules
    This skill should be used when the user asks to \"update rules\", \"sync rules\", \"update AGENTS.md\", \"update CLAUDE.md\", \"refresh rules\", \"update project config\", \"sync templates\", \"update vibe rules\", \"check for rule updates\", \"update user rules\", \"update…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.