skills.rest
fimmtiu
fimmtiuCOMMUNITY
Explore all skills by this author →
GitHub

cf-respond

Automate code-review change requests from cf-tickets with lint and tests.

2|Updated Mar 22, 2026
Search Tags:#automation#lint#code-review#tests#ticket-management#respond#cf-tickets
One-click install
npx skills add https://github.com/fimmtiu/code-factory --skill cf-respond
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cf-respond
Source: https://github.com/fimmtiu/code-factory/tree/main/skills/cf-respond
Command: npx skills add https://github.com/fimmtiu/code-factory --skill cf-respond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates responding to code-review change requests on a tracked ticket by orchestrating the change-request workflow, applying fixes, and reporting results.

Core Features & Use Cases

  • Fetch and enumerate open change requests for a specified ticket from cf-tickets.
  • Validate each request, write or update tests, implement changes, and ensure code health via lint and tests.
  • Commit changes with a cf-respond-prefixed message including the change-request ID and ticket, then close the loop with a concise summary.

Quick Start

Provide the ticket identifier after the trigger to begin processing its change requests.

Frequently Asked Questions about cf-respond

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

FAQPage Schema
How do I automate responding to code-review change requests?▼

You can automate responding to code-review change requests by using a tool that fetches requests from ticket management systems, applies fixes, runs tests, and commits changes with a ticket identifier prefix.

What is the best way to handle code review changes and run tests automatically?▼

The best way to handle code review changes automatically is to orchestrate reading request details, evaluating necessity, updating tests and implementation, and running pre-detected lint and test commands before committing.

How does a cf-respond prefix work when committing code review fixes?▼

A cf-respond prefix works by tying the commit message to the specific ticket identifier, ensuring traceability when applying and committing code-review change requests from your ticket management system.

Do I need to manually run lint and test commands after applying change requests?▼

No, you do not need to manually run lint and test commands because the system pre-detects available testing and linting commands and executes them automatically after updating the implementation.

Can I use this to fetch and enumerate open change requests for a specific ticket?▼

Yes, you can fetch and enumerate open change requests for a specified ticket by providing the ticket identifier, which starts the process of validating and applying each requested change.

What is included in the summary after automating code review responses?▼

The summary after automating code review responses is a concise post-action report detailing the fetched change requests, applied fixes, test results, and final commit information tied to the ticket.

Related Skills

Explore More Software Engineering Skills→
terrazul-aiterrazul-ai

response-draft

Generate draft responses for batches of open tickets using templates.

Official
Advanced
vanducngvanducng
5

code-review

Generate inline GitHub PR comments and a summary verdict for code changes.

Community
Intermediate
gensart-projsgensart-projs

lint-and-validate

Run lint and static analysis tools on Node.js and Python projects.

Community
Intermediate
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic