Skip to main content
Manusで任意のスキルを実行
ワンクリックで
GitHub リポジトリ

skills

skills には con から収集した 12 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。

収集済み skills
12
Stars
2
更新
2026-06-19
Forks
2
職業カバレッジ
5 件の職業カテゴリ · 100% 分類済み
リポジトリエクスプローラー

このリポジトリの skills

introduce-codespell
ソフトウェア開発者

Introduce codespell spell-checking to a project. Creates branch, config file, CI workflow (GitHub Actions or Forgejo Actions for Codeberg), pre-commit hook. Lists typos, helps identify paths/words to ignore, and fixes typos interactively. Use when setting up codespell in a new project.

2026-06-19
introduce-reuse-compliance
ソフトウェア開発者

Introduce REUSE specification compliance (LICENSES/ directory, REUSE.toml, SPDX headers) to a software project or BIDS dataset, then validate it. Covers BIDS data-vs-code separation, DUO (Data Use Ontology) integration, DEP-3 patch tagging for vendoring repos, and integration with tox / pre-commit / Makefile / GitHub Actions. Use when adding licensing metadata to a project, fixing `reuse lint` failures, licensing a BIDS dataset, or annotating patches in a vendoring repo.

2026-06-01
introduce-git-bug
ソフトウェア開発者

Introduce git-bug distributed issue tracking to a git project. Configures GitHub bridge, syncs issues, pushes refs, and documents workflow in DEVELOPMENT.md and CLAUDE.md. Use when setting up git-bug in a new project.

2026-05-17
credit-contributions
高等教育人類学・考古学教員生化学者・生物物理学者

Annotate a paper or work with CRediT (Contributor Roles Taxonomy) author contributions and render the LaTeX byline. Creates a `.tributors.credit.yaml` overlay (single source of truth, compatible with con/tributors), seeds it from sibling repos' git history when present, renders the "Author Contributions" section into LaTeX or Markdown for the target venue, emits JATS XML for publisher metadata, and (via render_authors.py) renders the `\author{}` block with affiliation references. Use when a paper needs a CRediT statement, when standardising contributor attribution across a multi-repo work, when authors need an auto-generated byline + affiliation block, or when the user mentions CRediT / NISO Z39.104 / contributor roles / author contribution section.

2026-05-16
pr-feedback-review
ソフトウェア品質保証アナリスト・テスター

Load a PR's review feedback (human + bot) **and CI status**, classify each comment, and recommend what to address vs dismiss with draft responses. CI failures (merge conflicts, lint, tests, workflow runs) are first-class — diagnose, propose a fix, and bundle into the same actionable report. Works from a local repo directory or a PR URL.

2026-05-08
pr-review-update
ソフトウェア品質保証アナリスト・テスター

Review dashboard PRs needing your response and generate high-confidence update proposals for PRs where maintainers are waiting

2026-04-29
github-project-status
プロジェクト管理専門家

Check the health and maintenance status of a GitHub project. Use when user asks about project status, whether a project is maintained, abandoned, or looking for alternatives. Analyzes commit history, releases, issues, PRs, and searches for active forks or community discussions about project future.

2026-04-29
analyze-duplicates
ソフトウェア品質保証アナリスト・テスター

Analyze codebase or documentation for code/text duplication using jscpd. Generates a Markdown report with collapsible sections (suitable for GitHub/Gitea issues) showing duplicate clusters, statistics, and a mediation plan proposing refactoring strategies.

2026-04-07
scan-projects
ソフトウェア開発者

Scan subdirectories and files to create/update projects.tsv with metadata and LLM-generated summaries

2026-04-03
bisect-and-patch-git-annex
ソフトウェア開発者

Bisect git-annex regressions using tinuous CI logs, create reproducers, generate fix patches, and submit Red/Green PRs to datalad/git-annex. Use when investigating test failures in git-annex CI, creating reproducer scripts, or preparing upstream bug reports.

2026-03-10
issue-triage
ソフトウェア開発者

Triage open GitHub issues by cross-referencing against codebase and git history

2026-03-06
tinuous-analyzer
ソフトウェア品質保証アナリスト・テスター

Analyze con/tinuous CI log collections to identify test regressions, compare successful vs failing runs, and provide investigation recommendations. Use when users mention test failures, CI regressions, or need to understand what changed between CI runs.

2026-02-20