Automate triage, classification, and routing of GitHub issues and pull requests.
npx skills add https://github.com/hachej/boring-ui --skill boring-triage
Please help me install this Agent Skill. Skill: boring-triage Source: https://github.com/hachej/boring-ui/tree/main/.agents/skill-library/kanzen/v1/boring-triage Command: npx skills add https://github.com/hachej/boring-ui --skill boring-triage
This Skill eliminates the manual overhead of managing GitHub issue and PR lifecycles by automating state classification, gate checking, and routing decisions.
Use the boring-triage skill to analyze the current GitHub issue and determine the next required action.
High-intent search queries and answers about installing and using this skill.
To automate GitHub issue triage, this Skill classifies risk, refreshes issue and pull request metadata, and identifies the next required gate to enforce consistent workflow routing. It eliminates manual overhead by validating state and labels based on project-specific procedures.
Enforcing gate-based development cycles is achieved by applying project-specific procedural documentation to validate state, labels, and proof requirements for pull requests. This ensures adherence to procedures like grill, plan, implement, and proof before routing.
Yes, you can classify risk for fast-track merging by using this Skill to verify if a pull request meets policy rules. It evaluates risk and determines whether a PR qualifies for fast-track merging or requires an owner review.
Yes, automated pull request triage requires integration with the GitHub API to refresh metadata and validate state. It also requires project-specific procedural documentation to ensure accurate classification and routing decisions.
You should not use automated triage if your project lacks defined procedural documentation for gate-based development cycles. The routing decisions rely on project-specific procedures to validate state, labels, and proof requirements accurately.
Automated issue classification needs project-specific procedural documentation to accurately validate state, labels, and proof requirements. Without these defined procedures, the Skill cannot enforce consistent gate-based development cycles or make risk-aware routing decisions.
AIS-Commercial-Business-UnitAutomate design handoff from Figma to AIS using the Figma API and design tokens.
yocxy2Merge pull requests and verify production deployment health with canary checks.
alexeybanPlan, implement, and document DevOps changes within software delivery pipelines.
yusaduymazTriage GitHub issues and pull requests against repository templates and guidelines.
