Plugin "punchtape": repo updated since submission - please rescan

Open Beginner friendly
#578 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
76/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github, typescript

Research direction

Start by reading the repository’s plugin submission and auto-scan flow; the issue names the source skill at skills/punchtape/SKILL.md and the current source commit 318f5b5. Check how rescans are queued and how the plugin card receives scanned content. Done when the punchtape card reflects the current repository state and its pending verification can proceed.

Written by the indexing model from the issue text.

Description

Hi! I submitted the punchtape plugin (https://cursor.directory/plugins/punchtape, source repo: https://github.com/neurophant/punchtape) via the auto-scan flow.

Since submission the skill in the repo (skills/punchtape/SKILL.md) has been updated in two rounds: remote-document links removed, and new notes added - explicit command inspection before execution, install footprint, and explicit authorization before acting on a zone found in a parent directory (current head: https://github.com/neurophant/punchtape/commit/318f5b5).

The plugin card still shows the earlier scanned content. Could you queue a rescan so the card picks up the current repo state? A verification request is also pending on my side. Thanks!

Dominant language
TypeScript
Stars
4k
Forks
671
Avg merge
7m
Merged PRs (30d)
32

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cursor/community-plugins

All issues in cursor/community-plugins

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.