grapple

Redirect legacy `/grapple` commands to the preferred `/review` workflow.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/prompted365/context-grapple-gun --skill grapple
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grapple
Source: https://github.com/prompted365/context-grapple-gun/tree/main/cgg-runtime/skills/grapple
Command: npx skills add https://github.com/prompted365/context-grapple-gun --skill grapple

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a legacy entry point for the CogPR + Warrant review flow, ensuring continuity for existing workflows while encouraging the adoption of the preferred /review command.

Core Features & Use Cases

  • Legacy Command Support: Accepts the /grapple command as an alias for the /review command.
  • User Guidance: Informs the user that /grapple is a legacy command and directs them to use /review.
  • Use Case: A user who is accustomed to the older /grapple command can still invoke the review process without interruption, while being gently guided towards the current standard.

Quick Start

Run the grapple skill to initiate the review process.

Frequently Asked Questions about grapple

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

FAQPage Schema
How do I run the CogPR + Warrant review workflow using legacy commands?

The legacy command supports continuity by accepting your input and notifying you to use the preferred review command. It provides redirection and user guidance without executing direct functional processing.

What happens when I trigger a legacy command alias instead of the preferred review command?

Triggering a legacy command alias provides redirection and user notification rather than direct functional execution. It informs you of the legacy status and directs you to the current command structure for the actual workflow.

Can I still use older workflow commands for docket and warrant review processes?

Yes, you can still use older workflow commands for docket and warrant review processes. The legacy alias ensures continuity for established habits while gently guiding you towards adopting the current standard command.

Does the legacy command alias execute the review process directly?

No, the legacy command alias does not execute the review process directly. It performs no direct functional execution, serving only to redirect users and provide notification to use the preferred command.

Why should I transition from legacy workflow commands to the current review command structure?

You should transition from legacy workflow commands to the current review command structure to ensure you are using the actively supported functional execution path. The legacy alias only provides redirection and user notification.