critique

Run githooks, linters, tests, and branch safety checks before committing.

4|5|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fartybobo/farty-bobo --skill critique-fartybobo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critique
Source: https://github.com/fartybobo/farty-bobo/tree/main/skills/critique
Command: npx skills add https://github.com/fartybobo/farty-bobo --skill critique-fartybobo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill enforces gated reviews, githooks, and branch safety so commits and pushes never bypass essential validation. It also coordinates reviewer selection, PR creation, and Jira transitions to keep teams aligned and accountable throughout the change lifecycle.

Core Features & Use Cases

  • Repository detection & validation: Locate impacted repositories from context or human selection, then run githooks, linters, type checks, and tests before any commit can proceed.
  • Review orchestration: Prompt the human for critic selection, gather markdown revision reports, offer Codex or manual review routes, and enforce decision-making before implementation moves forward.
  • Commit, PR, and Jira compliance: Enforce ticket-prefixed commits, branch safety checks, once-approved pushes, automated PR opening, Jira transition, and Decision Log posting with explicit human consent.

Quick Start

Ask the skill to inspect currently affected repos, run githooks, and walk you through the branch, commit, review, PR, and Jira steps before pushing.

Frequently Asked Questions about critique

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

FAQPage Schema
How do I enforce githooks and code review before a commit is pushed?

To enforce code review before a commit, use a gated workflow that runs githooks, linters, and tests, then verifies branch safety and reviewer approval before allowing any push to proceed.

How do I automate Jira ticket transitions when opening a pull request?

Automating Jira ticket transitions when opening a pull request requires coordinating ticket-prefixed commits, PR creation, and explicit human consent to trigger Jira state changes. This keeps team accountability aligned throughout the change lifecycle.

Can I use manual review routes alongside automated code checks for pull requests?

Yes, you can use manual review routes alongside automated code checks. The workflow gathers markdown revision reports and offers manual or automated review routes, enforcing decision-making before implementation moves forward.

What is the best way to manage branch safety across multiple affected repositories?

The best way to manage branch safety across multiple affected repositories is to locate impacted repos from context, run validation checks, and enforce branch policies and hooks before proceeding. This guarantees safe commits across your project scope.

Do I need to prefix my commits with a Jira ticket number for PR creation?

Yes, you need to prefix your commits with a Jira ticket number for PR creation. The workflow enforces ticket-prefixed commits, branch safety checks, automated PR opening, and Decision Log posting with explicit human consent.