Claude Skill

pull

Look at the remote and pull a clean repository that is behind; after a pull of the engine, the Action required lines crossed and the offer of the checks

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download pche-broken-artist-forge-of-thought-.claude_skills_pull-3ef759b.zip · 0 KB

Install

skills CLI npx skills add https://github.com/pche-broken-artist/forge-of-thought/tree/main/.claude/skills/pull
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install pche-broken-artist-forge-of-thought@llmmart
Git git clone https://github.com/pche-broken-artist/forge-of-thought.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole pche-broken-artist/forge-of-thought collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Pull the forge from its remotes through scripts/forge-pull.py (POS.1490, SOL.0180): the scripts are the only door to a write of git (CLAUDE.md, Persistence). The forge looks and offers; it pulls only what is clean and behind, merges nothing and runs no check unasked. $0 is one repository (forge = the engine, a slug = that project); bare = the engine and every project with an origin.

  1. Run python scripts/forge-status.py --remote and report the state of each repository in scope in the words of POS.1490: up to date, behind, ahead, diverged, no origin, not under git. A repository with unsaved changes or with a diverged history stops here, with its one offer: /save first, or a merge by hand or by /save (which rebases the user's commits onto the remote). Nothing is pulled from it.
  2. For what is clean and behind, run python scripts/forge-pull.py $ARGUMENTS and relay its report: where each repository moved from and to, and the subjects of the commits between.
  3. After a pull of the engine, read RELEASE-NOTES.md and show the Action required lines of every release whose commit the script listed (release <version>); then offer /check light <slug> and /check project <slug> on each project the user keeps (POS.0940), and run them only on his word. Where an Action required line names a migration, offer /migrate <slug> for each project the user keeps that is of the shape before the migration (templates/project.md); the one-clone rule is CLAUDE.md's (Persistence) and the script's.
  4. After a pull of a project, report what the script printed.
Files (forge-of-thought)
  • SKILL.md 1.8 KB
    ---
    description: Look at the remote and pull a clean repository that is behind; after a pull of the engine, the Action required lines crossed and the offer of the checks
    argument-hint: "[project-slug]"
    disable-model-invocation: true
    ---
    
    Pull the forge from its remotes through `scripts/forge-pull.py`
    (POS.1490, SOL.0180): the scripts are the only door to a write of git
    (CLAUDE.md, Persistence). The forge looks and offers; it pulls only what is clean
    and behind, merges nothing and runs no check unasked. `$0` is one
    repository (`forge` = the engine, a slug = that project); bare = the
    engine and every project with an origin.
    
    1. Run `python scripts/forge-status.py --remote` and report the state
       of each repository in scope in the words of POS.1490: up to date,
       behind, ahead, diverged, no origin, not under git. A repository
       with unsaved changes or with a diverged history stops here, with
       its one offer: `/save` first, or a merge by hand or by `/save`
       (which rebases the user's commits onto the remote). Nothing is
       pulled from it.
    2. For what is clean and behind, run `python scripts/forge-pull.py
       $ARGUMENTS` and relay its report: where each repository moved from
       and to, and the subjects of the commits between.
    3. After a pull of the engine, read `RELEASE-NOTES.md` and show the
       Action required lines of every release whose commit the script
       listed (`release <version>`); then offer `/check light <slug>` and
       `/check project <slug>` on each project the user keeps (POS.0940),
       and run them only on his word. Where an Action required line names
       a migration, offer `/migrate <slug>` for each project the user
       keeps that is of the shape before the migration
       (`templates/project.md`); the one-clone rule is CLAUDE.md's
       (Persistence) and the script's.
    4. After a pull of a project, report what the script printed.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.