ci-failure-debugging Skill
Debug and fix failing CI validation checks for this Python project. Use when asked to fix CI failures, debug failing PR checks, fix pylint/mypy/black/cspell/pytest errors, or when a PR validation workflow fails. Published by microsoft in FeatureManagement-Python.
Decision snapshot
Is this a fit?
Testing, Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is ci-failure-debugging Skill?
Debug and fix failing CI validation checks for this Python project. Use when asked to fix CI failures, debug failing PR checks, fix pylint/mypy/black/cspell/pytest errors, or when a PR validation workflow fails. Published by microsoft in FeatureManagement-Python. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Data analysis
- Testing use cases
- Data analysis use cases
Declared skill metadata
- Source file: .github/skills/ci-failure-debugging/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use ci-failure-debugging Skill
- Use it for testing.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/FeatureManagement-Python
- Skill file: .github/skills/ci-failure-debugging/SKILL.md
What it does
Debug and fix failing CI validation checks for this Python project. Use when asked to fix CI failures, debug failing PR checks, fix pylint/mypy/black/cspell/pytest errors, or when a PR validation workflow fails.
Skill instructions
CI Failure Debugging This project's PR validation runs the following checks on Python 3.10–3.14. To debug failures, identify which step failed and follow the corresponding section below. Step 1: Identify the failing check The validation workflow runs these steps in order: 1. black — code formatting 2. pylint — static analysis 3. mypy — type checking (strict mode) 4. cspell — spell checking 5. pytest — unit tests with coverage 6. pylint (samples/tests) — lint samples and tests with relaxed rules Step 2: Reproduce locally Set up the environment first: bash python -m pip install -e ".[dev,test]" Then run the specific failing check: | Check | Command | Notes | |-------|---------|-------| | pylint | pylint featuremanagement | | | black | black --check featuremanagement | Use black featuremanagement to auto-fix | | mypy | mypy featuremanagement | Uses strict = True from mypy.ini | | cspell | npx cspell "" | Config in cspell.config.yaml, custom words in project-words.txt | | pytest | pytest t
Verified compatibility and discovery
Frequently asked questions
What is ci-failure-debugging?
ci-failure-debugging is a open-source AI agent skill with Copy skill directory. Debug and fix failing CI validation checks for this Python project. Use when asked to fix CI failures, debug failing PR checks, fix pylint/mypy/black/cspell/pytest errors, or when a PR validation.
Who is ci-failure-debugging best for?
ci-failure-debugging is best for reusing agent instructions, scripts, and references, testing workflows, data analysis workflows.
How do I install ci-failure-debugging?
Install or run ci-failure-debugging using Copy skill directory. Check ci-failure-debugging for the latest setup command.
Is ci-failure-debugging actively maintained?
ci-failure-debugging may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
