forge

Enforces self-contained PR prose, git-based merges, and forge audit discipline for hosted repositories.

10|2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/nrdxp/predicate --skill forge-nrdxp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge
Source: https://github.com/nrdxp/predicate/tree/main/skills/forge
Command: npx skills add https://github.com/nrdxp/predicate --skill forge-nrdxp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When AI agents open, review, and merge pull requests on GitHub, GitLab, or Forgejo, PR bodies often leak process-internal references, merges bypass consent, and out-of-scope findings vanish without a durable record. This Skill defines the discipline that keeps the forge a clean, self-contained public record. ## Core Features & Use Cases - Branch-to-PR mapping: Defines per-node PRs against a shared integration branch plus one tracking PR per campaign, including the forced bootstrap order and stacked PR handling. - Self-contained PR prose: Enforces a two-question test (what is this work, how do I review it), soft-wrapped formatting, SHA-pinned permalinks, and a mechanical check_forge_prose.sh gate before posting. - Merge consent and git-only merges: Merges happen in the git CLI with the head's explicit consent; the forge observes and records but never performs the merge. - Forge audit and tracking issues: A composer-owned checklist at merge-consent and campaign close, plus meta tracking issues and mandatory criticality labels for out-of-scope findings. - Use Case: An agent finishing a campaign node pushes its branch, opens a node PR with self-contained prose, posts review findings as impersonal comments, merges locally in git after consent, and files every deferred finding as a linked, tagged issue. ## Quick Start Use the forge skill to draft a self-contained PR body for my current branch and check it with the forge prose gate before opening the pull request.

Frequently Asked Questions about forge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a self-contained pull request description?

Write PR prose that answers only two questions: what is this work and how do I review it. Exclude all process-internal references, soft-wrap paragraphs as single logical lines, and pin any links to commit SHAs rather than branch names.

Should I merge pull requests with the GitHub merge button or git CLI?

This discipline requires merging with the git CLI locally, then pushing so the forge detects and closes the PR. The forge merge API constrains strategy to squash, rebase, or single-merge shapes and manufactures commits outside commit-gate hygiene.

Does this forge discipline apply to repositories without a remote forge?

No. Applicability is conditional: projects with a bare remote, patch workflow, or no remote have no obligations. The test is whether the origin remote resolves to a forge the project accepts contributions through.

How do I handle stacked pull requests when a base branch merges?

Base each stacked PR on its prerequisite branch. When the base merges and is deleted, the dependent PR retargets or may auto-close as closed rather than merged; annotate it with the merge commit so the record reads correctly.

What labels should AI agents add when opening GitHub issues?

Follow the project's existing label scheme exactly where one exists; otherwise apply a minimal set covering type, criticality, and obvious component. Security-critical and correctness-critical issues must always carry their criticality tag, or a title prefix where labels are unsupported.