Create and track GitHub Issues from user observations via GitHub CLI.
npx skills add https://github.com/carllelandtaylor/facto --skill observe-carllelandtaylor
Please help me install this Agent Skill. Skill: observe Source: https://github.com/carllelandtaylor/facto/tree/main/plugins/facto/skills/observe Command: npx skills add https://github.com/carllelandtaylor/facto --skill observe-carllelandtaylor
This Skill simplifies the process of capturing product observations, automatically creating GitHub Issues, and managing them for efficient tracking.
Run /facto:observe in the terminal to capture your observation.
High-intent search queries and answers about installing and using this skill.
You can automatically create GitHub Issues from product observations by logging your notes and classifying them as bugs, features, or chores. The Skill then generates and routes the issues to GitHub, ensuring they are categorized correctly for tracking.
GitHub issue tracking integrates with project status management by monitoring issue statuses through GitHub project integration. This allows you to automatically track the progress of generated issues directly within your existing GitHub workflows.
Yes, you need the GitHub CLI (gh) installed and authenticated to automate issue creation and tracking. The Skill utilizes this dependency to route observations, generate issues, and manage their status on your GitHub repositories.
The best way to log and categorize product observations for GitHub is to capture your notes and immediately classify them as bugs, features, or chores. This triggers automatic issue generation and applies predefined categorization rules for accurate routing.
Yes, you can use predefined rules to categorize GitHub Issues automatically. The Skill applies these rules during issue creation based on your initial observation classification, ensuring the generated issues are routed and labeled correctly.
If your automatically generated GitHub Issues are not tracking status correctly, it may be due to missing GitHub project integration or an unauthenticated GitHub CLI session. Proper status monitoring requires a valid gh authentication to access and update project boards.
georgekhananaevWrap GitHub CLI commands with risk classification and confirmation prompts.
CalcMarkManage GitHub issues and project boards with the GitHub CLI.
LLM-Dev-OpsAutomate GitHub project board synchronization and sprint planning via swarm coordination.
elihunter173Automate Jira issue creation via CLI commands with customizable fields.
