“contributions”的搜索结果

Schools of historical thought, methodology debates, and the philosophy of history. Covers the major historiographical traditions (Annales, Marxist, feminist, postcolonial, subaltern, world-systems), their methodological commitments, their contributions and limitations, and the enduring debates about objectivity, narrative, and the nature of historical knowledge. Use when evaluating how different historians approach the same subject, understanding why historical interpretations change over time, or assessing the theoretical framework underlying a historical argument.

中文简介正在准备中。当前显示原文说明。

Drafts or audits a scientific paper's introduction: real-world motivation, evidence audit, theory-to-if-then funnel with a named estimand, bridges across experiments, and calibrated contributions. Use to write, frame, or critique an introduction.

中文简介正在准备中。当前显示原文说明。

Find actual code issues in a repo that aren't listed in GitHub issues. missing tests, inconsistent patterns, outdated dependencies, documentation gaps. Presents findings to the user for evaluation. Use when you want to make proactive contributions beyond existing issues, or when no good issues are available. Not for browsing the existing issue tracker. Use oss-find-issue for that.

中文简介正在准备中。当前显示原文说明。

Plan and execute your second and third contributions to become a regular contributor. Covers relationship building, progressive complexity escalation, and community presence. Use when your first PR was merged and you want to keep contributing, when transitioning from one-off contributor to regular, or when planning a sustained OSS involvement. Not for your first contribution — use the oss-find-issue → oss-contribute chain for that.

中文简介正在准备中。当前显示原文说明。

Find unclaimed open source issues that match the user's skills and experience level. Searches for issues created by maintainers/org admins, checks contribution eligibility, and ranks by learning value. Use when looking for an issue to contribute to, starting OSS contributions, or finding GSoC-friendly issues. Not for finding problems that nobody has filed an issue for yet. Use oss-find-real-issues for that.

中文简介正在准备中。当前显示原文说明。

Evaluate whether an OSS repo is worth long-term investment before committing time. Assesses project health, governance, community, bus factor, and trajectory. Use when deciding whether to contribute to a specific repo, choosing between multiple repos, or evaluating a project's sustainability. Not for checking if a repo accepts contributions — use oss-find-issue for that.

中文简介正在准备中。当前显示原文说明。

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

中文简介正在准备中。当前显示原文说明。

Generate changelog for ArchitectKB template contributions

中文简介正在准备中。当前显示原文说明。

Structures capital call execution with notice preparation, pro-rata allocation, default remedy provisions, and wire coordination. Use when processing capital calls, calculating LP contributions, or managing call logistics.

中文简介正在准备中。当前显示原文说明。

Evaluates GP capital commitment levels with co-invest obligations, management company funding, and alignment assessment. Use when analyzing GP commitment, assessing alignment, or structuring GP capital contributions.

中文简介正在准备中。当前显示原文说明。

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective".

中文简介正在准备中。当前显示原文说明。

30/60/90 Day Onboarding Plan — Day 1 setup, week 1 ramp, month 1 milestones, month 2 contributions, month 3 evaluation criteria

中文简介正在准备中。当前显示原文说明。

Writes expert academic paper summaries for social science research, particularly political science and applied statistics. Use when asked to summarize, review, or create a reading summary of an academic paper, PDF, or research article. Accepts a file (PDF or text format) or a directory of papers. Produces a structured markdown summary — approximately 400–600 words — covering primary contributions, major questions and answers with point estimates, methods and data, and limitations and robustness. Includes BibTeX citation retrieved from Google Scholar and keyword metadata.

中文简介正在准备中。当前显示原文说明。

Assesses a research paper outline (.qmd file) against structured criteria from Kosuke Imai's empirical research guide. Evaluates the abstract and section outline for: research question clarity, stated contributions, hypotheses and testable implications, data description, planned results and inferential approach, and robustness checks. Detects causal papers from the abstract and conditionally assesses identification strategy only when causal framing is present. Produces a structured markdown report with PASS/PARTIAL/FAIL assessments and actionable suggestions. Use when asked to assess, evaluate, review, or check a paper outline, abstract-and-outline, or research plan in a .qmd file.

中文简介正在准备中。当前显示原文说明。

"Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas. Use when asked for weekly retro, what shipped this week, or engineering retrospective.".

中文简介正在准备中。当前显示原文说明。

Writing biosketches that build reviewer confidence — personal statement, contributions, and honest positioning.

中文简介正在准备中。当前显示原文说明。

Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.

中文简介正在准备中。当前显示原文说明。

Weekly-cadence engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. NOT for per-session or per-task reflection (see mk:memory / Phase 6 Reflect).

中文简介正在准备中。当前显示原文说明。

Expert-level volcanology covering volcanic processes, eruption styles, volcano monitoring, volcanic hazards, igneous petrology, and volcanic contributions to climate.

中文简介正在准备中。当前显示原文说明。

Builds a compact profile of a GitHub user or PR author — identity, activity, company, commit history, and trust signals. Use during pull request review or triage, especially for contributions from unfamiliar authors.

中文简介正在准备中。当前显示原文说明。

Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.

中文简介正在准备中。当前显示原文说明。

Record the statements a journal requires and a reader checks — authors with their CRediT contributions, ethics approval that names the body and the reference number, how consent was taken, funding with grant numbers, conflicts of interest, data availability with an address or a reason, and the use of generative AI — as a validated record that the submission folder prints and the manuscript never carries. Use when a run is heading for submission, when an author asks who should be listed, when consent, approval or data sharing has to be stated, or when the venue's AI policy comes up.

中文简介正在准备中。当前显示原文说明。

We, like many other open source projects, are dealing with a surge in low quality contributions enab

中文简介正在准备中。当前显示原文说明。

Complete guide to using and extending Hermes Agent — CLI usage, setup, configuration, spawning additional agents, gateway platforms, skills, voice, tools, profiles, and a concise contributor reference. Load this skill when helping users configure Hermes, troubleshoot issues, spawn agent instances, or make code contributions.

中文简介正在准备中。当前显示原文说明。